From page map to public page
Use the open core to model content, compose a page, preview its real renderer, and release it deliberately. Manage Ease is the separate managed path.
Read the setup guideThe onboarding sequence
Inspect the core
Start with the repository, license, setup guide, and current block contracts.
Run a test tenant
Configure the API, database, starter app, and tenant-owned storage in a non-production environment.
Map the routes
Give each page a distinct question, source facts, links, and a next action.
Compose in the editor
Use supported blocks, real media, and a compiled theme to build and preview the page.
The publishing loop
Validate
Check every page and block against the current schema and review links and media.
Preview
Inspect desktop and mobile output, accessibility, metadata, and the selected theme.
Approve
Use the required independent review for the exact draft revision.
Verify live output
After an authorized release, inspect readback, cache, robots, sitemap, and public forms.
A clear division of responsibility
Know what is managed and what remains under your control.
Developers own contracts
Extend schemas and renderers together when the current blocks are not enough.
Learn more →Workflow questions
What to expect as the site changes.
Start from a working contract
Follow the docs and build one representative page before expanding the site.
Read the documentation