Extensions
GJS ships a lean core. The blocks, tools and themes that make it your builder come from extensions, managed under Landings → Extensions.
The extension manager
A single admin screen lets you:
- Browse the GJS Market catalog and filter by category
- View detail cards with screenshots, ratings, install counts and changelog
- Install / enable / configure / remove any extension
- See an update badge when newer versions are available
Extension types
| Type | What it is |
|---|---|
| Preset | An entire editor theme. One active at a time; can replace the engine. |
| Plugin | Tools and behaviour — panels, commands, integrations. |
| Theme | A curated visual system for the pages you build. |
| Blocks | Drag-and-drop building blocks. |
Installing
There are four ways to install, and every one ends in a verified, browser-ready bundle:
- From the marketplace — one click; the signed bundle is sha512-checked against the catalog before it runs.
- From npm — a CDN fast-path resolves the package's browser build, or the build service compiles it.
- From a Git repo — the build service clones, builds, signs and publishes the artifact.
- From upload — a
.js,.zipor.tgzfrom your machine (capability-gated, like WordPress's own Upload Plugin).
Only browser-runnable bundles are installable; React/Vue/SDK packages are recognised and documented rather than executed blindly.
Configuring
Installed extensions expose a settings form right in their detail view. Curated per-extension schemas render friendly fields; an advanced JSON editor is always available for anything else.
Framework assets
Some blocks need peer dependencies they don't ship — Bootstrap, jQuery, Popper. GJS supplies these automatically in the canvas and on the front end, so a block extension "just works". You can override this per extension.
Updating
The manager checks the catalog for newer versions and surfaces an update count. Updates are atomic: new versions install into their own folder and old ones are pruned.
Trust
The plugin talks only to GJS Market and its build service — never directly to npm or GitHub. Read more in Security and the marketplace overview.