Applying or changing a page template

Documentation / Templates and reusable content

Applying a template changes how the page is assembled. It is not simply a visual preset pasted over an independent page body. Review existing content and the target template's editable areas before changing the binding.

Set the page choice

Open the page metadata and find Advanced > Page template override. Select the intended template and save. Reopen the page editor to inspect the resulting structure and available editable areas.

The current selector includes None (no template). Treat this carefully: clearing the explicit page choice does not necessarily mean no template will render. The engine can still inherit a template from an ancestor page or the collection's default. Check those sources when a template continues to appear.

Understand selection order

An explicit page template takes precedence. Without one, the renderer checks ancestor page paths for a template, then checks the page's collection default. A move or route change can therefore alter inherited template behavior.

Custom body design is incompatible with a template-bound page. Do not expect selecting a template to convert custom HTML into native editable content.

Protect page content

Compare the editable-area codes used by the old and new templates. Page-specific content is stored by code; an area with a different code is not automatically the same destination. Do not assume changing templates migrates ordinary body blocks or maps every old editable area into the new design.

Preserve a recoverable content state before the change. After saving, check the header, shared sections, editable content, images, and resolved URL. Test a visitor-facing page as well as the editor.

For revisions and recovery limits, see Saving, recovery, and troubleshooting.