Site structure — pages, sections and where your copy lives

The unit of work is not a page. It is a section inside a page inside a site.

The three levels

1. Site — one customer, one SiteTheme (accent, font, mode, radius), shared

across every page.

1. Page — identified by its slug (home, pricing). The slug is the

outside address; the internal id belongs to the platform, not to the model.

1. Section — one stack element with a kind. The engine and the editor both

produce sections; nobody hand-writes HTML.

Why slugs matter more than ids

An engine page's URL is its slug, not its id. Email links, custom-domain redirects and analytics keys all carry the slug, so renaming a slug is a re-routing event, not a damage event — and the platform keeps the old slug editable until you delete it deliberately.

Where drag-and-drop fits

The studio's visual editor edits the same SiteSpec the engine reads. Nothing in the pipeline is a picture of the state — there is one source of truth, and every surface reads and writes it.