Managed blocks versus custom design in assistant edits

Documentation / Agentic editing and connections

Managed pages store native Beeboo sections and blocks. Their text, images, Rows, and other supported content remain available to the visual editor. Custom pages replace the body with validated HTML and scoped CSS; the visual body editor then treats that source as read-only.

Preserve managed editing when possible

Ask the assistant to read the current page and retain existing section and block identities. JuBody is the body wrapper, JuSection is a top-level body section, and JuBlock is a content child. A request to restyle one block should not silently replace the whole page with custom source.

Text children should remain Markdown. Layout and text-alignment properties belong on the relevant objects, not inside improvised HTML text values. Preserve the real header on regular pages and keep navigation membership in the root structure.

Understand custom conversion

A custom body is a fragment, not a complete HTML document. It must not duplicate the website navigation, footer, or document wrappers. CSS is scoped, arbitrary scripts and inline event handlers are rejected, and interactions use supported behavior modules.

The default custom scope is body-only. Header-and-body work changes the content inside the real header and must retain its identity and title binding. Custom bodies are rejected on template-bound pages so locked template content cannot be bypassed.

Conversion does not maintain a synchronized native copy. Later edits must use the current custom source. Returning to managed authoring requires reviewing and restoring appropriate earlier content.

Save and verify

Assistant page updates save directly, using expectedPageModifiedAt for conflict protection; custom changes require it. The CMS retains separate reviewed-draft controls under Custom design. Do not confuse those controls with MCP page saves or editor cloud autosave. See page anatomy, templates, and saving and recovery.