Design system overview
Open Settings → POM Theme → Design system to manage visual settings shared by the current site. The available subsections are focused on reusable presentation rather than the structure or content of an individual page.
Design system subsections
| Subsection | Responsibility |
|---|---|
| Theme preview | Shows representative palette, typography, button, form, and notice output in one place. |
| Brand | Stores logos, the Site Icon, site identity display choices, shared interface icons, and social profiles. |
| Color palette | Defines 15 numbered colors used by palette selectors throughout the theme. |
| Fonts | Selects a safe fallback and manages custom font families and their variants. |
| Buttons | Defines the default button and additional named button styles. |
| Icons | Creates libraries of standalone SVG files for compatible icon selectors. |
| General styles | Controls the page canvas, main text and links, body type, paragraphs, headings, and display headings. |
| Components | Enables the Inner Row content toggler and defines success, notice, and error colors. |
How settings are applied
The design system establishes shared defaults. A more specific template, component, row, column, or page setting can override them. When a global change is not visible:
- confirm that the correct site and subsection were saved;
- inspect the affected component for an explicit local value;
- reload the public page while signed out;
- clear only the active page or asset cache when stale output remains.
Preview has a defined scope
Theme preview displays representative examples, including the palette, font families, headings, paragraphs, forms, buttons, and notices. It does not reproduce every template, plugin state, content length, or responsive combination.
Use it to catch broad inconsistencies, then verify a real page, archive, form, and WooCommerce screen when those areas are part of the site.
Related settings
Header, mobile navigation, subheader, breadcrumbs, and footer settings live under Site layout. Form-specific presentation lives under Forms. Page composition belongs in Page Builder. Keeping these scopes separate prevents a local adjustment from becoming an accidental site-wide rule.