Site-wide design and shared content

Documentation / Site administration and domains

A site-wide setting can affect many pages at once. Before changing it, decide whether the target is native design, reusable page-template content, a shared content region, or a custom shell. These layers have different editing and recovery boundaries.

Use the native settings first

Open Settings > Design for shared design controls. Fonts selects the body, heading, and optional accent families. Settings includes capitalization and page-animation choices. Shared topline and footer settings have their own entries. Review representative pages after saving rather than judging the result on a single homepage.

A page or section may have more specific design settings. If a global change appears not to apply, check inheritance and explicit local choices before repeating the save. A custom page can also use its own scoped CSS while retaining the site's selected font variables.

Distinguish templates and shared chrome

A page template supplies reusable page content and locked areas. Shared toplines, prefooters, and footers surround page content. A custom shell supplies selected shared presentation regions, including navigation and an optional shared page header. It normally works with native editable bodies; it does not require converting every page to custom HTML.

Review shell changes separately

Where supported by the deployment, Settings > Design > Shell provides advanced source controls. Save shell draft does not change the active design. Preview the exact saved source, confirm review, and Publish revision. A separate Activate reviewed revision switches the site to that immutable revision.

Check native and custom pages, translations, mobile navigation, and pages with local headers before activation. Returning to native can be blocked if a page explicitly requires a shared site header. See design and styling, templates and reusable content, and saving and recovery.