Custom page design: body only or header and body

Documentation / Design and styling

Custom page design replaces the managed body with reviewed source. The optional scope determines whether custom header source also renders inside the real page header. It does not replace the website's routing, access controls, or surrounding navigation and footer.

Prerequisites

Confirm that the active deployment supports custom design. A reviewed custom body must already exist before the scope selector is useful. Header and body additionally requires retained, reviewed custom header source. The scope selector is not a tool for automatically converting a managed page.

Custom design is not supported on template-bound pages. Resolve that architectural choice deliberately rather than removing template constraints to get access to a selector.

Change scope

Open the page metadata's Custom design area. Choose Body only (default) or Header and body, then select Save scope draft. Open Open saved draft and review the exact saved state at desktop, tablet, and mobile widths.

Confirm I reviewed this saved draft before using Publish reviewed scope. Use Discard scope draft if the saved scope is not suitable. Existing saved edits can block a scope change until they are reviewed or discarded.

Switching to body only retains the custom header source. It changes what renders, not whether that source remains stored.

Editing boundaries

Custom content remains read-only in the visual editor. The real header block stays outside JuBody, and canonical title metadata continues to identify the page. Source updates should preserve unrelated page metadata and use the current revision context.

Verify the normal visitor-facing page after publication. Check that the header is neither missing nor duplicated and that native shared chrome still works.

See Agentic editing and connections for authorized source editing.