Page templates and shared site design

Documentation / Templates and reusable content

A page template defines reusable page structure. Shared site design defines the presentation and regions around page content. They can work together, but changing one does not automatically change the other.

What a template owns

A template supplies blocks such as the real page header and body sections. Named Editable areas accept page-specific content. When rendering a bound page, Beeboo combines the template with that content and permitted overrides.

Template selection can come from the page itself, an ancestor page, or the collection's default template. The same template can therefore affect pages that do not each carry an explicit local selection.

What belongs to the site

Site fonts and theme colors are shared settings. Native toplines, prefooters, and footers reference dedicated shared content pages. Main navigation uses the configured root structure and page metadata rather than the template's body content.

An optional custom shell can replace selected shared regions, including navigation and the page header. It leaves the page body and engine-owned responsibilities intact. Confirm active deployment support before relying on this advanced feature.

Choose by responsibility

For service pages with the same structure and different copy, use a page template with editable areas. For one contact strip displayed beneath many pages, consider shared prefooter content. For a common navigation presentation, inspect site design rather than duplicating menu markup in a template.

Custom page bodies are not supported on template-bound pages. A custom shared shell with a native template-bound body is a separate arrangement and must respect both editing boundaries.

After a shared change, check pages with different content lengths, translations, and local overrides. See Design and styling for shared shell behavior.