Glossary
New to GJS Builder? These are the words that show up most often across the docs, each explained in one or two plain sentences. Skim it once and the rest of the documentation reads faster.
GrapesJS
The open-source editor engine GJS Builder is built on. It provides the drag-and-drop canvas, the layers panel, and the code view. GJS Builder wraps GrapesJS in WordPress and adds a marketplace around it. See The editor.
Core
The small WordPress plugin you install. On its own it does very little — it hosts the GrapesJS engine and coordinates everything else. All the real capability arrives as extensions. See How it works.
Extension
Anything you add on top of the core: a block, a panel, an integration, an SEO provider. Extensions are installed at runtime from the marketplace, so new features don't require a plugin update. See Extensions.
Preset
A ready-made editor setup — a bundle of blocks, panels, and defaults that turns the blank editor into one tuned for a job (a landing-page builder, a shop page, a portfolio). Only one preset is active at a time. See Presets & themes.
Theme
A visual skin — colors, fonts, spacing — applied to what you build. A theme changes how a page looks; a preset changes what tools you get. See Presets & themes.
Block
A single draggable piece you drop onto the canvas: a heading, a button, a pricing table, a hero section. Blocks are the smallest building unit in the editor.
Marketplace (GJS Market)
The catalog you browse and install from, right inside the editor. It offers presets, plugins, themes, and blocks, and can pull packages from npm, Git, or a direct upload. See Marketplace.
Dual-save
Every time you save, GJS Builder stores two things: the editable project (so you can keep editing) and the finished HTML/CSS (so the page can render). The finished HTML is also copied into WordPress's own post_content. See Storage & no lock-in.
Portable HTML
The plain, standards-based HTML your pages are saved as. Because it lives in post_content, your pages keep rendering through the theme even if you deactivate the plugin — nothing is trapped in a proprietary format.
No vendor lock-in
The promise that follows from portable HTML: GJS Builder is a build tool, not something your live site depends on. You can turn it off, export everything, or move on without breaking your pages.
Render mode
How a published page is served to visitors. GJS Builder offers two modes — one that outputs a self-contained page and one that renders through your theme — with zero JavaScript runtime either way. See Rendering modes.
White-label
Rebranding the whole editor and catalog as your own for clients: your presets, your marketplace endpoint, your name. Ideal for agencies handing off a clean build. See White-label.
Supply chain
The path an extension travels before it runs in your browser. GJS Builder only talks to GJS Market and its build service — never directly to npm or GitHub — and every bundle is checksum-verified before it loads, so you know exactly what you're running. See Security.
SEO provider
The component that writes a page's SEO tags (title, description, Open Graph, structured data). GJS Builder ships its own, but automatically steps aside when Yoast, Rank Math, or All in One SEO is active, so tags never duplicate. See SEO.
Build service
The service that turns any package — from the marketplace, npm, Git, or an upload — into a verified, browser-ready bundle the editor can load. It's what lets the marketplace stay open without shipping raw, unchecked code to your site.