Component-based editing
Assemble page bodies from reusable components — an FAQ block, a comparison table, a callout — without touching markup.
SolutionsFOR CONTENT TEAMS
Assemble and update pages without opening an engineering ticket.
Engineers define the content model and bind templates once. From there, editors work in a structured editor — components, dynamic zones, rich fields — while templates handle layout automatically. A thousand pages read like one editorial voice, not a thousand one-off drafts stitched together by hand.
01 / STRUCTURE, NOT HTML WRANGLING
A real editor, not templates in disguise
Rich field types and reusable components give editors genuine structure to work in. Rearranging a page body means picking blocks from an allow-listed dynamic zone — not opening a template file.
One model, every page consistent
Every page bound to a content type inherits the same structure, so voice and layout stay consistent at volume.
Multi-locale from the start
Translate a field, not a whole page rebuild — locales are structured data, not duplicated pages.
02 / EDITORIAL CADENCE, DECOUPLED
Draft, review, schedule — on your timeline
Draft/publish workflows and scheduled publishing mean editorial review and release timing don't have to happen in the same breath as a deploy.
Draft & review workflows
Move a record through draft and review states before it's eligible to generate a live page.
Scheduled publishing
Set a publish time once and let it go live on schedule — no one has to be online to hit publish.
One edit, every dependent page
Update a source record once and every page bound to it can be identified and rebuilt — no page-by-page manual updates.
GIVE EDITORIAL A STRUCTURE
Set up your first draft-to-publish flow.
Open a workspace and move a record from draft through review to a scheduled publish.