Page and section design inheritance

Documentation / Design and styling

The appearance of one section can come from several layers. Site fonts and colors provide a common base. A page can override its palette. A template can supply structure and body spacing, while individual sections and blocks retain supported local settings.

Inheritance does not mean every control overrides every earlier layer. Different settings have different responsibilities, and ordinary CSS inheritance still applies in custom designs.

Trace the responsible layer

If several pages share the same issue, inspect the website theme, fonts, template, or shared shell before making page-by-page changes. If one Text block differs, inspect its Text style and Font role. If one Row looks different, inspect its surface, padding, and gap settings.

In Page colors, disable Override website colors when the page should follow the website palette again. The change enters the page's editing state and needs a page save to publish.

Template-bound pages combine template body settings with permitted page settings. The renderer fills named editable areas from page content and retains template-controlled content elsewhere. Do not copy the rendered template into local page blocks to simulate an override.

Shared shell defaults

Where a shared shell is supported and active, it can also supply styles for native content. Its optional layered defaults have different precedence from ordinary unlayered source CSS. This is an advanced source contract, not a universal “page always wins” rule.

After changing a default, test an inheriting page and a page with explicit local choices. Reopen the saved page to ensure the result is not only an editor preview. Include a translated page if colors or shared source are involved.

See Templates and reusable content for template ownership.