EMPIREYO
← Insights
Web designupdated 12 November 202616 min read

Design systems: one source of truth

A button here, a slightly different blue there, three kinds of cards on one site. A design system puts an end to that.

In short

A design system is one source for design and code: tokens (colours, type, spacing), components with all their states, patterns and guidelines, with accessibility built in. A small site of a few pages needs only a light version. If your site keeps growing, has several languages, a light and a dark theme or an area behind a login, a full set fits better.

A website rarely grows according to plan. A campaign page is added, then a new form, then a second language. Each time someone picks a button, a colour and a spacing, and each time it comes out slightly different. After a few years your site has four kinds of buttons and three shades of your own blue, and nobody knows which one is right.

A design system prevents that. In this article you will read what it is, how it differs from a style guide or brand guide, what goes into it, when a small business site needs one and when it is too much, how to build and maintain it, and what you can expect at handover.

What is a design system?

A design system is the fixed set from which every screen of your site or app is made, together with the rules for using it. It has four layers:

  • Tokens: the smallest design decisions with a name, such as a colour, a font size or a spacing.
  • Components: the parts you use again and again, such as a button, an input field, a card or a notification.
  • Patterns: fixed combinations of components for a task, such as a form with error messages or a row of cards with a filter.
  • Guidelines: when to use what, and why.

The key word is “one”. Design and code draw from the same source. If the main colour changes, it changes in one place, and every button, link and heading that uses it changes with it. That is why a design system is often called a single source of truth.

How does it differ from a style guide, brand guide or component library?

The terms get mixed up, which makes quotes hard to compare. This is how they relate:

NameWhat it containsWho it is forWhere it lives
Brand guideThe logo and how to use it, the colours with their codes, the typefaces with their licences, imagery and tone, with the reason behind every ruleYou, your colleagues, your printer and your photographerA document
Style guideColours, typography and components, recorded for the websiteWhoever maintains or extends the siteA document or page
Component libraryThe components themselves, ready to useDesigners and developersA design tool or the code
Design systemEverything above for the screen, plus patterns, guidelines and the link between design and codeEveryone who makes or changes a screenDesign files, code and documentation together

A brand guide covers your whole brand, including on a van or a business card. A design system covers screens. It takes the colours and type from the brand guide, but also settles things a brand guide does not: what a disabled button looks like, what happens when a field is filled in wrongly, and which shade of green is readable enough on a white background. You can read more about the brand guide under branding. How to keep both consistent is in consistent brand identity in 2026.

What does a design system give you?

Four things, if it is kept up to date:

  • One face. Every page looks the same, including the page that is added two years from now.
  • Fewer decisions per page. Whoever makes a new page chooses from existing components instead of designing again.
  • Changes in one place. A new colour or a larger font size is changed once, not on forty pages.
  • A shared language. Designer and developer call a component by the same name, so there is less guessing during the build.

You often hear that a new page then takes hours instead of days. How much time it actually saves depends on the site and on who maintains it. We have not measured that, so we do not give a number.

What goes into a design system?

Tokens: design decisions with a name

The W3C Design Tokens Community Group, a group of designers, developers and makers of design tools, describes a token as information with a human-readable name, at minimum a pair of name and value. On 28 October 2025 the first stable version of their specification (2025.10) was published. It sets out how to write tokens in a JSON file, so that design tools and code can exchange them. The format includes, among others, tokens for colour, dimension, font family, font weight and duration.

The value lies in the layers. The documentation of Material Web, the web components of Google’s Material Design, describes three kinds of tokens: reference tokens with a fixed value, such as a colour code, system tokens that define a role, and component tokens for a single component. A button then does not use “green #1C6A45”, but “the colour for the main action”, and that role points to the colour code. In Material Web, tokens are CSS variables.

You can see those roles on our clients’ case pages. At Ikiz night blue carries the site, and sea green marks what you need to see, such as labels and buttons. At TaalPro orange is the colour of the buttons, and each language level has its own colour, from red-orange for A1 to amber for C1.

Components: parts with all their states

A button is not a single picture. It has states: default, pressed, disabled, and what appears when something goes wrong. An input field has more: empty, filled in, selected with the keyboard, error and valid. A good component has all of those states worked out, so the developer does not have to invent what an error message looks like. That is also the difference between a nice design and a usable system: the design shows the default state, the system shows every state.

Patterns: components together for a task

A pattern is a fixed solution for something that keeps coming back: a form in steps, a search field with results, a pricing block, a list of questions and answers. It records which components go into it and in what order. A new service page then does not need to be designed from scratch; it gets the same structure as the others.

Guidelines: when do you use what?

Guidelines are the short sentences that prevent misuse. One primary button per screen. The accent colour only on a dark background. Error messages say what is wrong and how to fix it. The words on buttons and in messages belong here too; you can read more in our article on microcopy.

Accessibility: in the system, not as an afterthought

This is where a design system gains the most. If you check the contrast once in the tokens, it is right on every page that uses them. The reverse is also true: a mistake in a token is everywhere at once. The requirements come from the WCAG, the guidelines of the W3C. For colour, these are the main ones at level AA:

WhatRequirementCriterion
Normal textA contrast of at least 4.5:1 with the background1.4.3
Large text: at least 18 point, or 14 point boldAt least 3:11.4.3
Components and their states, such as the border of a field or the mark that shows a box is tickedAt least 3:1 against the adjacent colours1.4.11
Graphical parts you need to understand the content, such as a line in a chartAt least 3:11.4.11
Where the keyboard focus isVisible on every component you operate with the keyboard2.4.7
Text in a logo, and disabled componentsNo contrast requirement1.4.3 and 1.4.11

According to the W3C you may not round the result: 4.499:1 is not enough. A colour that works well in your logo is therefore not automatically good enough for text. That is why a design system sometimes has two shades of the same brand colour: one for the brand and one for text. What the law asks for, you can read in our article on the Accessibility Act.

Does a small business site need a design system?

A light version, yes; a full system, by no means always. A site of five pages that you renew every few years needs no more than recorded colours, type, spacing and a handful of components. A set in which every component has all its states, with written patterns and guidelines, is a project in itself. That only makes sense if many screens are added or if more people work on it.

Your situationLight versionFull system
A site of a few pages that rarely changesFitsToo much
Pages or articles are added every monthFits, if the patterns are fixedFits
More than one language, or a language that reads right to leftMay get tightFits
A light and a dark themeMay get tightFits
An area behind a login, such as a portal or booking environmentToo littleFits
Several people or parties making screensToo littleFits
Several sites or brands built from the same componentsToo littleFits

An example of that last case is NL Design System, the Dutch public-sector initiative. It says itself that it is not an ordinary design system, but a collection of design systems from municipalities and government organisations, among others, which together find out which components work in practice. A brand identity can be recorded in it as a theme. That is the scale a full system is meant for. For most small business sites it is a size too big, but it shows clearly how tokens and themes work together.

What changes with a light and a dark theme?

With tokens, a second theme is not a second site. Each role gets its own value per theme, and the components stay the same. The work is in the checking: every combination of text and background has to meet the contrast requirements in both themes. A colour that reads well on white often does not on near-black.

Sittard Taxi has two complete themes. The site opens dark, a button switches it to light, and that choice is remembered. Someone ordering a taxi at night does not want to look at a bright white screen. Each theme has its own colours; the dark one is not an inverted light one. The accent is mint (#00C896) in the light theme and neon mint (#7CFFB4) in the dark one. Basestep, our own product, also has a dark and a light mode, with a button at the top of every page.

And with several languages?

Every language makes texts longer or shorter, and that has to fit in every screen. A button that fits in Dutch can run over two lines in German. A language that reads from right to left also mirrors the whole layout. At TaalPro every page exists three times, in Dutch, English and Farsi; the Farsi version mirrors the whole layout, with Vazirmatn as the typeface. A system that takes this into account from the start saves many separate fixes.

How do you build a design system?

We start with the tokens, then the core components, then the patterns that combine them. With us everything is made in Figma, from wireframe to design system with tokens and components. Step by step:

  1. See what is already there. On an existing site, collect every button, every field and every colour currently in use. That overview shows what is duplicated and what is missing.
  2. Set the tokens. Colours with a role, type with its sizes, spacing in a fixed scale. Check the contrast before it is fixed.
  3. Make the core components. Button, link, input field, checkbox, card, notification, menu. Each with all its states, including for the keyboard.
  4. Build the patterns. The fixed combinations for the tasks on your site: requesting, booking, searching, comparing.
  5. Carry it over into code. The same names and values as in the design, so what you see is what gets built. Spacing, behaviour and exceptions are recorded for the build.
  6. Write it down. For each component, when to use it and when not. Briefly, with an example.

Do not start with everything. The first version only needs what you need now. Whatever is added later connects to the same tokens. How this works in a full project, you can read under UI/UX design; for an ordinary website under web design.

“A design system is not a goal in itself, but an agreement that every next page leans on.”

How do you keep a design system up to date?

A design system that is not maintained ages faster than the site itself. Someone is in a hurry, builds a button outside the system, and a year later there are four again. Five habits keep it together:

  • One owner. Someone decides what goes in. That can be your developer, or someone in your own team.
  • Check the set first. If a new component seems necessary, first see whether an existing one can do the job. If not, add it to the system rather than to a single page.
  • Change the token, not the page. A colour adjusted by hand on one page gets lost at the next change.
  • Announce before you remove. Mark a component that has to go as deprecated first. The W3C specification even has its own field for that.
  • Check the contrast again. After every colour change, in every theme.

Small things you change yourself: a text, an image. Whoever adds a screen later takes from the fixed set. Larger changes to the structure go through us, or through a maintenance plan if you would rather hand it over.

What do you get at handover?

Ask every agency, including us. This is what comes as standard with us:

  • A style guide: colours, typography and components, recorded. It is one of the three documents you receive with every handover, next to an admin manual and technical notes.
  • The design files in Figma, with full access. On payment they are put in your name, just like domain, code and data.
  • A handoff to the build with spacing, behaviour and exceptions. That applies to our own build, but also if another party builds.
  • With a brand identity project, your colours and type also as code, so a developer can use them directly.

Only our general building blocks stay ours. How the six phases of a project run, you can read in our process. For a small site of a few pages a light version is enough, and we will say so.

When this does not apply

If you have a site of a handful of pages that rarely changes, a full design system is mostly extra work. Recorded colours and type and a few fixed components are enough. If you work with a bought theme in an existing system, that theme already decides a lot; a design system of your own next to it can mean double work.

What we do not know: we have not measured how much time a design system saves our clients. Contrast is only one part of accessibility; automated tests find nowhere near all problems, and ArtsenPool too still describes itself as partially compliant. The format of the Design Tokens Community Group became stable in October 2025; which tools already read it in full, we have not checked.

Frequently asked questions

What is a design system?+
The fixed set from which every screen of your site or app is made: tokens such as colours, type and spacing, components such as buttons and fields with all their states, patterns for tasks and guidelines for use. Design and code draw from the same source.
What is the difference between a design system and a style guide?+
A style guide records colours, typography and components. A design system goes further: it adds patterns and guidelines, works out every state of each component and links the design to the code, so that a change in one place carries through everywhere.
Does a small website need a design system?+
Usually a light version is enough: recorded colours, type, spacing and a handful of components. A full system only fits a site that keeps growing, has several languages or themes, an area behind a login, or several people making screens.
What are design tokens?+
Design decisions with a name, such as a colour, a font size or a spacing. On 28 October 2025 the W3C Design Tokens Community Group published the first stable version of a format to exchange them between design tools and code.
How much contrast should the colours in a design system have?+
Under WCAG 2.2 at level AA, at least 4.5:1 for normal text and 3:1 for large text. Components such as the border of an input field, and graphical parts you need to understand the content, need at least 3:1 against the adjacent colours.

Wondering how much system your site needs? Tell us how big it is and who maintains it, and we will tell you whether a light version is enough. What it costs is on our pricing page. You work directly with Nawid, with a fixed team of five specialists.

Sources

Consulted on 3 November 2026.

NR
Nawid RasaFounder of Empireyo · in design, development & strategy since 2014

Also worth reading: The UX mistakes that cost you customers in 2026.

Written with the help of AI, reviewed and edited by Nawid Rasa, who is responsible for the content. Sources are listed below the article. Spotted an error? Email hi@empireyo.com.

Ready for design that converts?

We design around your user and build a design system that grows with you.

What do you have in mind?
What budget do you have in mind?
When do you want to launch?
Almost there. How do we reach you?
Request sent.

Your request has reached us. You will usually hear back within two working days. Prefer direct contact? Email hi@empireyo.com or message us on WhatsApp with the chat button at the bottom right.

Reply within two working days · No obligation · privacy