
Building Design Systems for Web Applications with Figma, Storybook, and npm
Build design systems for web apps with Figma tokens, Storybook components, npm packages, release discipline, supply‑chain care, and team adoption.
Articles
Design systems are the shared decisions that keep front‑end work coherent as an interface grows. They cover components, design tokens, states, accessibility expectations, documentation, and the boring but valuable rules that stop every new screen becoming a one‑off negotiation between design and code.
Below you will find a subset of articles from my blog specifically about Design Systems. This is a topic I have worked with for many years, although it has not been one I have written about often. There are six articles collected here so far, which you can see and read below.

Build design systems for web apps with Figma tokens, Storybook components, npm packages, release discipline, supply‑chain care, and team adoption.

A retrospective on React component APIs before hooks settled, covering render props, higher‑order components, context, classes, and migration judgement.

Build accessibility into reusable front‑end components with names, keyboard behaviour, focus states, form semantics, disabled states, and testing habits.

How Storybook can document front‑end components, states, edge cases, accessibility checks, and design conversations outside the main application.

Manage colours, spacing, typography, breakpoints, and component values in front‑end code without scattering design decisions or weakening consistency.

Use BEM and Sass together for component CSS with clear naming, shallow nesting, modifiers, reusable mixins, and less fragile front‑end styling over time.