DE Skip to documentation

Content and editing

Shared headers and footers

Create reusable site chrome and assign it by language, page type or article category.

On this page

Create a shared layout

Administrators use Design → Headers & footers to create named headers and footers, duplicate them and edit them visually or as sanitised HTML. A saved global layout affects every page assigned to it. Choose the layout's language and assignment scope deliberately. Only one rule may occupy a given type/language/scope combination. An explicit page selection must match that page's language.

Assignment precedence

  • Explicit page or article selection.
  • Article-category assignment.
  • All pages or all articles in the language.
  • Language-wide default.
  • Original theme layout as fallback.

Choose Use global assignment to return a page to rule-based selection. Custom header links remain part of that layout unless the navigation token is used.

Supported tokens

text
[care:navigation]
[care:certifications]

The navigation token inserts the active theme's menu and language switcher into a custom header. The certifications token supplies a custom footer position when that placement mode is selected. Stored tokens do not execute PHP, Twig or arbitrary template code.

Upgrade legacy footers

After a backup and the required migrations, run the repeatable import during a quiet editing period:

shell
php bin/console app:layouts:import

Equal sanitised footers in the same language share one layout. Original footer HTML remains as fallback; existing shared layouts are not overwritten. Reload any editor opened before the upgrade rather than forcing an outdated save.

Something unclear? Contact me about this guide.