Six inconsistent microsites consolidated into one design system

Each service line had commissioned its own site, so the brand appeared in three type scales and four blues. Nobody could say which version was current, and every new page started with a copy-paste of the last one.

Engagement

Role: Brand and design system engagement.

Shape: Audit, token definition, component build, written handover.

Duration: Two to three weeks for the design system tier.

Stack: Figma library · Design tokens (HSL) · Tailwind CSS · WCAG 2.2 AA · Component documentation.

What was wrong

  • Three type scales and four brand blues were in simultaneous use across live sites.
  • No shared component names, so design and engineering described the same element differently.
  • Contrast failures in secondary text and focus states that were invisible to keyboard users.
  • New pages were produced by duplicating the previous page, carrying its mistakes forward.

What was built

  1. Audit of every existing page pattern, reduced to a single component inventory with names the team agreed on.
  2. Colour, type and spacing tokens defined once in HSL and shared between the Figma library and the Tailwind config.
  3. Accessible component set covering navigation, forms, cards and tables, with focus states and reduced-motion behaviour specified.
  4. Written usage guide so a new designer or developer can extend the system without asking what the intent was.

Architecture after the work

Tokens defined once — Colour, type and spacing tokens live in one HSL source and are consumed by both the Figma library and the Tailwind configuration.

Named component inventory — Navigation, forms, cards, tables and callouts have one agreed name and one implementation, documented with the states each supports.

Accessibility as a default — Contrast, visible focus, keyboard order and reduced-motion behaviour are specified in the component itself rather than added per page.

Extension guide — A written guide records the intent behind each decision so a new designer can extend the system without reverse-engineering it.

Trade-offs and what was left out

  • Illustration style was intentionally left out of the first pass — it was not blocking page production and needed a separate budget.
  • Two low-traffic microsites were redirected rather than redesigned, which was cheaper than migrating their content.

Outcome

One source of truth for the brand in both design and code, with the previous microsite URLs mapped into the consolidated structure.

Frequently asked questions

Do we need a design system for a small site?
Not always. A design system pays for itself once more than one person produces pages, or once the same pattern exists on more than a handful of screens. Below that, a documented page template is usually enough.
Who owns the Figma library afterwards?
You do. The library, the token source and the usage guide are handed over in your own Figma and repository, with no licence conditions attached.

Related services