GJS Builder
Getting startedInstallationThe editorPages & LandingsExtensionsPresets & themesRendering modesSEOPerformanceStorage & no lock-inSecurityDeveloper APIWhite-labelRoadmapFAQGlossary
Back to docs

Pages & Landings

GJS Builder keeps a strict boundary around your existing content. It works only through its own Landings post type — never your posts, pages or the Gutenberg editor.

Why a separate post type

  • No conflicts. Your regular editing workflow is untouched.
  • Clear ownership. It's obvious which content is built with GJS (the Landings list shows a "Built with builder" column).
  • Safe permalinks. Landings only claim root-level slugs that no real Page or Post already owns.

Creating a Landing

Landings → Add New, set a title, and open the builder. Clicking Edit or Add New on a Landing takes you straight into the fullscreen editor rather than the classic editor.

Landings get clean, root-level permalinks (/your-slug/). The plugin resolves these at request time and defers to any real Page or Post that owns the same slug, so there are no collisions.

The list table

The Landings list works like any WordPress list: search, bulk actions, statuses. The extra "Built with builder" column makes GJS pages easy to spot.

Where content lives

Each Landing stores two things on save: the editable project JSON and the compiled HTML/CSS, with the HTML mirrored into post_content. That mirroring is what lets your pages render even if the plugin is deactivated — see Storage & no lock-in.