Skip to content
SiteMonk Learn
Esc
↑ ↓ navigate ↵ open ⌘J preview
On this page
  1. From values to purposes to components
  2. Why purpose matters more than appearance alone
  3. Judge usefulness when pages are added

Design tokens: give shared rules useful names

Understand design tokens through values, purposes, and components, and see how shared settings support consistency.

Many parts of a website share colors, type sizes, and spacing. If each is set independently, a brand color update can miss a few buttons. A design token is a named, reusable design value that different parts of the site can reference.

Think of it as a named settings list for the website. You do not need to maintain the list, but understanding it helps explain future updates and why related components share rules.

From values to purposes to components

These hypothetical names explain the layers; they are not a mandatory naming standard.

Layer What it records Example
Primitive token An available underlying value A particular blue or spacing step
Semantic token The purpose of a value Primary action color or body text color
Component token A setting for a specific interface part Primary button background

Semantic means purpose here. A button background can reference “primary action color,” which references a base blue. A small site may use fewer layers. Add component-specific settings when independent adjustment is useful.

Why purpose matters more than appearance alone

“Body text color” describes a job; “dark gray” describes its current appearance. On a dark background, body text may need to become light while its purpose stays the same. Purpose-based names help the team understand the impact of a change.

Naming does not replace judgment. Links, decoration, and status messages may need different rules even if they currently share a blue. Equally, giving every individual gap a new name adds maintenance work without necessarily helping.

Judge usefulness when pages are added

Imagine adding a new service. Reusing heading and primary action settings helps it fit existing pages. If price conditions need a different treatment, the team first considers existing rules before creating an exception.

Ask which settings are shared, which pages a change affects, and who checks them. The team maintains names, references, and code. Tokens coordinate settings; they do not automatically make content clear, forms functional, or every layout suitable.

Continue with applying rules to web pages and themes , or see the whole design system . For a professional reference, see USWDS design tokens .

For our website builds , shared foundations support the agreed design and future page additions. We choose the implementation; you review whether it keeps your content and customer actions consistent.