Page Shells

What Page Shells are for

A Page Shell supplies inherited layout and document settings to every attached page. Use one for shared navigation, footers, promotional bands, favicons, head scripts, or export behavior.

Sections in the ordered zone merge into each attached page’s section list. Their content stays shared, while each page controls its placement order independently.

What Page Shells can control

A Page Shell belongs to one organization and can be attached to many pages. A page may inherit multiple shells in a deliberate order.

• Top sections that always render before page-specific content.
• Ordered sections that mix with direct page sections and can be dragged to a different position on every page.
• Bottom sections that always render after page-specific content.
• Head scripts from every active shell, followed by the page’s own scripts.
• Favicon and export-head behavior from the first active configured shell.

Ordering and overrides

Shell order on the Page form controls inherited-setting precedence. Each page stores its own order for sections in the ordered zone.

• Top and bottom sections sort by shell order, then their order inside the shell.
• Ordered sections appear in the normal Sections index and can be dragged alongside direct page sections.
• Direct page sections win equal-order ties in the ordered zone.
• If the same Section is inherited and directly placed, it renders once using the direct page placement.
• Editing a shell section updates every page that inherits it.

Related concepts

Page Shells affect rendering. Categories classify pages for filters and integrations, while page tags organize pages in their deployment destination.