Header and footer globals
Editor fields of the Header and Footer globals and how RootHeader / RootFooter render them.
On this page
Header and Footer are globals shared by the site's pages. Their fields store navigation and content; RootHeader and RootFooter render them using Systhema components.
HeaderLink to this section
Enable the global with header: true, or configure its object form in Plugin options. Header data has two tabs:
| Field | Behavior |
|---|---|
navigation | Array of required labels with either a link or sub-navigation items. |
navigation[].subNavigation | One nested array of labeled links. |
cta | At most two calls to action using ButtonBlockFields. |
Links select a custom URL or Page relationship and can open in a new tab. The site logo is part of the frontend layout, rather than an upload field on this global. Use the Header component to customize its rendering.
FooterLink to this section
footer: true enables the simple layout. Use footer: { enabled: true, type: 'advanced' } for grouped main navigation.
| Field | Behavior |
|---|---|
content | Slot-tier rich text shared by both layouts. |
simpleNavigation | Labeled custom or internal links in the simple layout. |
main | Advanced layout blocks: a titled navigation group or titled slot-editor content. |
bottomNavigation | Additional labeled links in the advanced layout. |
social | Required icon and URL per social link. |
copyright | Text shown in the copyright area. |
The configured footer type controls which navigation tabs appear. RootFooter renders the chosen Footer component layout.
Locale-aware logo linksLink to this section
On a localized site, the layout's logo links use the current locale's homepage. Page relationship links use localized paths and the configured homepage rewrite. See Rendering pages.
AccessLink to this section
Enabled globals allow public reads for frontend rendering. Authenticated reads require global.header.read or global.footer.read; updates require the matching .update capability. The built-in admin role includes these through global.*. Disabling either global removes its editing interface.
Publishing and revalidationLink to this section
Both globals support drafts, autosave and scheduled publishing. Publishing chrome changes invalidates the site's layout cache because every route can render it. See Revalidation.