Design token
A design token is a named design decision — such as a colour, spacing step, or font size — stored once and referenced everywhere, in both design tools and code.
Tokens are the smallest unit of a design system. Because every screen references the token rather than a copied value, a single change propagates everywhere at once, keeping design and code in sync as a product scales.
How it works
Tokens usually come in two tiers. Primitive tokens name raw values, such as blue-600 or space-4. Semantic tokens name purposes and point at primitives, such as color-action pointing at blue-600. Components reference only the semantic tokens, so changing what "action" means, or adding a dark theme, is a change in one place.
Tokens are stored in a neutral format such as JSON and transformed into CSS custom properties, native app values and design-tool variables, so every platform reads the same source.
Example
troiana.net keeps its tokens as CSS custom properties at the top of one stylesheet: a single accent colour, --signal, used only for interactive elements, plus the type and spacing scale. Every page and generated section reads those variables rather than hard-coding a colour.
In practice
Ask your developer to show you where the brand colours, fonts and spacing live in the code. If the answer is one file or one settings panel, the site uses tokens in practice, even if nobody calls them that. If the colour appears in dozens of stylesheets, any visual change will cost more than it should, and it is worth consolidating before a redesign. In design tools, the equivalent is shared styles or variables rather than colours picked by eye on each screen.
Token names deserve a short conversation, because they outlive the values. Names that describe a role, such as primary action, error or page background, survive a rebrand; names that describe a value, such as dark blue, become wrong the day the blue changes. Keep the set small: a business site usually needs a handful of colours, a type scale and a spacing scale, not hundreds of tokens. When accessibility issues appear, such as text with poor contrast, fix them in the token so every page that uses it improves at once. That only works if the code consistently references tokens instead of raw values.
Why it matters for your business
Tokens are what make a visual change cheap. If your brand colour is stored once as a token, a refresh, a seasonal campaign or a fix for poor contrast is a single edit that reaches every page and app screen. If the colour is copied into hundreds of places, the same change becomes a search-and-replace project with misses. Tokens also make adding dark mode realistic, because each role simply points at a different value. Before commissioning a redesign or a new colour palette, it is worth asking whether the current site uses tokens: the answer changes how much of the work is design and how much is tedious rework.
Common mistakes
- Naming tokens after their value (
blue) instead of their role, so a rebrand breaks the meaning. - Creating a token for every one-off value until the set is as messy as the code it replaced.
- Keeping design-tool variables and code tokens in two unsynchronised places.
Questions people ask
Are design tokens the same as CSS variables?
Not quite. A design token is the named decision itself, such as the primary action colour, stored in a neutral format. CSS custom properties, often called CSS variables, are one common way of delivering those tokens to a website. The same tokens can also be exported to mobile apps and design tools, which plain CSS variables cannot do on their own.
Do I need design tokens for a WordPress site?
You may already have a simple version. Many modern WordPress themes keep global colours, fonts and spacing in a central settings file that the editor and every block read from, which works much like a basic token set. Use those global settings instead of picking colours block by block, and changes stay consistent.
Who creates design tokens, the designer or the developer?
Both, ideally together. The designer decides the values and their roles, such as which colour means action or error. The developer sets up the format and the build step that turns them into code. Tokens fail when only one side owns them, because design files and code then drift apart.