Design systems0 to 1

ADEK Design System

ADEK

One design system for every ADEK product: designed in Figma, shipped as code for React and Angular, and documented in one place both designers and developers use.

Role
Design systems lead, end to end and governance
Organisation
ADEK, Department of Education and Knowledge
Timeline
2026, ongoing
Deliverables
Figma libraries, adek-ui on npm, docs site
Users
ADEK designers, developers and vendors
Role

I lead the ADEK Design System end to end: the foundations and variables in Figma, the base and application component libraries, the shared CSS layer and the adek-ui Angular package, the documentation site, and the governance that keeps all of them in step.

Impact

ADEK teams and vendors design from one Figma library and build from one package, so a button, a table or a modal looks and behaves the same across every product, in English and Arabic.

ADEK Design System: the components overview on the docs site, and the button component set in Figma.
409Primitive variables behind every colour, space and radius
2Colour modes, light and dark, on 303 semantic variables
41Component pages in Figma: 15 base, 26 application
63Documentation pages with React and Angular code

Overview

ADEK builds many products for schools, parents, inspectors and staff, often with different vendors. Without a shared system, every team rebuilt the same buttons, tables and forms in slightly different ways, and every product drifted a little further from the brand.

The ADEK Design System fixes that at the source. The Figma libraries hold the foundations and components. A single CSS layer turns them into code shared by React and Angular, published as the adek-ui package. The documentation site shows every component with live previews and code to copy. I own all three, and the rules for how they change.

What I owned

A design system is only as good as its weakest handover. The work is making Figma, code and docs say exactly the same thing.

Objectives → Design framing

One source of truth

How might every ADEK product draw colour, type and spacing from the same variables, instead of copying values by hand?

Design and code in step

How might a component look the same in Figma, in React and in Angular, without three teams maintaining three versions?

Easy to adopt, hard to misuse

How might a new vendor go from zero to a correct ADEK screen in an afternoon?

Key constraints & tradeoffs

Two frameworks

ADEK products are built in both React and Angular. The system had to serve both without doubling the work or letting them drift apart.

Arabic first

Every component had to work right to left, with SF Arabic as the Arabic companion to Montserrat.

Accessibility for government

Colour pairs are checked against WCAG 2.2 contrast ratios, and every interactive element has a visible focus ring.

Many vendors, one brand

External teams build ADEK products. The system had to be self-serve: libraries, packages and docs they can use without a meeting.

How objectives translated to features

Why?

Hard-coded hex values are how brands drift. Variables make the right choice the easy one.

Design decisions
  • 409 primitive variables for raw values, and 303 semantic colour variables with light and dark modes on top.
  • Separate collections for spacing, radius, widths, containers and typography, so each has one job.
  • Electric Blue as the brand, with Sand and Light Gray scales, each swatch labelled with its contrast score.
  • 44 text styles and 24 effect styles, named the same way in Figma and in code.
Tradeoff

Two layers of variables take longer to set up than a flat palette. They are what make dark mode and future rebrands a change of values, not a redesign.

Solution

Layer 1

Designed in Figma.

Everything starts in two libraries: Core, with foundations and base components, and Applications, with the larger patterns products are built from.

ADEK primary colours in Figma with contrast ratios
01

A brand in variables

Electric Blue, Sand and Light Gray, each with its contrast ratio.

The primary colours page documents the brand as scales from 25 to 950, with every swatch labelled with its WCAG contrast score, so designers can see at a glance which pairs are safe for text.

  • Scales from 25 to 950
  • Contrast score on every swatch
  • Backed by light and dark mode variables
ADEK button component set in Figma
02

Every state, every size

Buttons across hierarchies, sizes and states, including loading.

Components are built as full variant sets: primary, secondary, tertiary and link hierarchies, four sizes, icon-only versions, and default, hover, focus, disabled and loading states. Designers pick; they never redraw.

  • Hierarchy, size and state as properties
  • Focus rings built into the component
  • A loading state with a Submitting label
Table with an empty search state from the application library
03

Application patterns, not just atoms

Tables, modals, charts, calendars and 22 more pages.

The application library covers what products are actually made of: page and card headers, navigation, tables, modals, command menus, charts, empty states and more. Each one is assembled from the base components, so a change to a button flows everywhere.

  • 26 pages of application components
  • Built from base components
  • Empty, loading and error states included

Layer 2

Shipped as code.

The same tokens and component styles serve React and Angular, so a product built by any team, in either framework, matches the Figma file.

Button documentation page with preview and code
01

Preview and code, side by side

Each component with its variants, previews and React and Angular code.

The button page walks through hierarchy, sizes, icons and states, each with a live preview and a code tab. The values are taken straight from the Figma variants, down to the padding and focus ring.

  • Live preview for every variant
  • React and Angular code tabs
  • Specs stated from the Figma source
Angular install guide with ng add adek-ui
02

One command to start

ng add adek-ui installs the package, styles and fonts.

Angular teams install the system with one command. The schematic adds the package, registers the stylesheets and adds Montserrat to the project, and every component is a standalone import.

  • ng add schematic
  • Standalone components
  • Manual setup documented too
RTL support guide with an Arabic form
03

Right to left, by design

Arabic and English from the same components.

The RTL guide shows the same form in Arabic and English and explains how components use logical CSS properties, so layouts mirror with the document direction instead of needing a second version.

  • Live Arabic and English toggle
  • Logical properties instead of left and right
  • SF Arabic as the Arabic typeface

Layer 3

Documented in one place.

The docs site is where designers, developers and vendors meet: what the system is, how to install it, and every component with code.

ADEK Design System introduction page
01

Start here

What the system is, the tech stack, accessibility and next steps.

The introduction explains the system in plain language, lists the supported stacks (React, Angular, CSS tokens, with .NET and vanilla JavaScript coming), and sets accessibility as the baseline for government services.

  • Supported stacks at a glance
  • Accessibility as a baseline
  • How it differs from a library
Components overview on the docs site
02

Everything at a glance

Every base and application component on one page.

The overview renders every component as a small live card, so people browse visually and click through to the full page, instead of guessing names in a sidebar.

  • Live thumbnails, not screenshots
  • Base and application components
  • One click to the full page
Tables documentation with a team members example
03

Real patterns, ready to copy

Application components with realistic content.

Application components are documented with realistic examples, like a team members table with avatars, statuses, badges and pagination, so teams copy a working pattern rather than assembling one from parts.

  • Realistic example content
  • Preview and code
  • Built from the same base components

Outcomes

3 in 1Figma, code and docs kept in step as one system
30+Components in adek-ui for Angular, with React code for each
EN · AREvery component built for left to right and right to left

Reflection

The hardest part of a design system is not the components, it is keeping promises. When the docs say a button has 8px radius and a Semibold label, that has to be true in Figma, in React and in Angular, today and after the next release. Leading the system end to end taught me that governance is mostly that: making sure every layer tells the same truth.

Got a gnarly problem? Let's untangle it.

Open to full-time roles and remote collaborations.

LinkedInRésumé (PDF)

Find all 5 hidden falcon secrets · 0/5 found

© 2026 Wakasso Idi

Falcon 3D model: “Falcon_ Merged Animations” by HectorBonada, CC BY 4.0