Choosing managed or custom design

Documentation / Getting started

Choose managed design when people need to edit the page visually. Native sections and blocks expose content and layout controls without requiring HTML or CSS. This includes text, media, Buttons, Rows, and supported dynamic blocks.

Choose custom page design when the approved layout needs source-based authoring and ongoing source maintenance is acceptable. A custom body replaces the native body structure with a reviewed HTML fragment and scoped CSS. It is not a visual conversion tool, and later source edits do not update a hidden native copy.

Decide what must remain editable

Ask who will maintain the content after the design is approved. A native body beneath a shared custom shell can retain visual editing while changing the surrounding site presentation. A page template can standardize native structure while exposing only named editable areas.

Custom body design is not supported on template-bound pages. Do not remove a template merely to bypass its locked content. Review the dependency and preserve content before making that architectural change.

Understand the scope

The Custom design selector offers Body only (default) and Header and body for an existing custom page. Header and body requires reviewed custom header source. The visual body editor remains read-only. The engine still owns navigation, routing, access checks, and document structure.

These advanced capabilities require support in the active CMS and engine deployment. Confirm availability before planning a production change. Review desktop, tablet, and mobile layouts, then test the saved visitor-facing page.

Read Design and styling for source limits and Templates and reusable content for shared native structures.