Page Builder

Build the page. Keep the design working.

Compose a page visually, ask your assistant to help, or bring custom React. Shared templates keep recurring pages consistent, while previews and publishing controls keep changes reviewable.

Explore plans /pricing See the platform /about

Choose the right level of control

Compose with the block catalog

Use the available page layouts and content blocks for everyday publishing. Adjust content and presentation in the editor, then check the result at the sizes your visitors use.

Use a shared page template

Bind pages to one published layout and give each its own content. Updating the template updates linked pages, so a family of features, comparisons, or program pages stays consistent.

Create reusable components

Save a useful component for reuse across the site. Use components for repeatable pieces and shared templates when the entire page structure should be maintained together.

Add custom React when you need it

Raw Code blocks support interactive web content within the runtime’s import and size limits. Supply the React Native and Markdown representations so the page remains useful across its supported surfaces.

Move from draft to a reviewed release

Validate the document, refresh its preview, review the revision, and check readiness before publishing. Use revision history and scheduled releases to manage changes deliberately.

Build through the UI or your assistant

The Page Builder and MCP expose the same authoring lifecycle: settings, document operations, templates, preview, review, and release. An assistant can work with structured tools rather than recreating a separate publishing path.

Cedros Pages overview with route, status, and page actions in an example workspace. /media/objects/9a4c293de52c5e9b0ad52744c10a01d94ccb5b4ecc04a5ec618315f30dc56742/retained/93f463cb-9995-5248-93ff-c3783201b190/assets/2026/09/bc567d73-6646-4667-a60c-932738568740.webp Real Cedros interface · example workspace data

Useful to know

Is starting from a design the same as a shared template?

No. A starter gives you an initial design. A shared template remains linked, so future layout updates propagate to the pages using it.

Can each page keep its own copy?

Yes. The page stores its field values separately from the shared layout.

Can I bring an existing application?

Adapt it into supported custom pages or extensions. Framework-specific servers and dependencies do not transfer automatically.

A better way to build and maintain the website.

Give authors a clear content workflow and developers room for custom work.

Talk about your website /contact