Skip to content
Design

Theming with CSS Variables: One Change, Whole Site

How Peerless maps theme settings to CSS custom properties so a single color change re-skins every page instantly.

The most expensive sentence in web maintenance is “the brand color changed.” On most sites that sentence costs a week of find-and-replace. On this one it costs a single setting.

Settings in, variables out

Every color, font, and spacing choice you make in theme settings compiles to a CSS custom property on the root element. Modules never hardcode a brand color; they reference the token.

Why editors should care

Rebrand day stops being a project. Change the primary color once and buttons, links, icons, and accents update across every page — including pages built long after the change.

It also keeps the CSS payload small: one definition, referenced everywhere, cached once.

Under the hood

Theme settings compile to custom properties on :root--primary-color, --heading-font, --border-radius and friends. Modules reference the tokens, never raw values, which is exactly the discipline the ITCSS settings layer exists to enforce.

Comments