All posts

The design system I've built over the years

The design rules, components and tokens I've built up over the years, now brought together in code with Radix, Tailwind and preset themes.

5 min read

Aa

Sessions over time

12.4k

+10.7% last mo
PaidPending-6%

Paid on time

81%

+4%

Overdue

€3,420

-6%
ClientAmount
Harbour & Co€4,500.00
Lindqvist Studio€1,250.00
Okafor Labs€980.00
PaidPendingDraftSent

We only use it for invoices.

K
Device: 2Region: 1Source: 1
  1. Harbour & Co paid

    11/03 · 14:42

    Paid
  2. Invoice sent

    10/03 · 09:12

    Sent
/pricing100% · 1,840
/checkout77.5% · 1,426
-22.5%
/checkout/pay30.3% · 557
-38.4%
AKJMSO
12

Invoices sent

248

+12%

Revenue

€48.2k

+6.1% last mo
⌘Kto search

Over the years, I've developed my own set of design rules, components and tokens that I reuse across projects. It started with individual decisions made while designing interfaces and gradually grew into a system I could rely on.

I recently brought it all together in code, building the components with Radix and Tailwind and adding themes for different products. The interactive demo below lets you explore the system, from colour scales and typography to individual components and layout rules.

Colour

The colour system follows a familiar approach, similar to Tailwind's numbered palettes. It includes a neutral scale, a primary colour scale, and separate scales for success, warning and error states.

Components reference these steps through design tokens. A surface might use neutral-50, a border neutral-200, and secondary text neutral-600. Each product maps those tokens to its own palette, so the same components can be used with different colour schemes.

October
3 invoices
Harbour & Co
Paid
Lindqvist Studio
Pending
Okafor Labs
Overdue
Send reminders
50100200300400500600700800900950
neutral
primary
success
warning
error
A dot marks a step the card uses.
Point at a part of the card to find its step, or at a step to find where it's used. Dark mode moves the colours, never the names.

Dark mode uses the same tokens with a different colour mapping, keeping the component styles consistent across both modes.

Typography

The typography system uses a fixed scale of sizes, a line height of 1.25 and two font weights. Letter spacing stays consistent, while the typeface can vary between projects.

The older products use Inter, while the analytics dashboard uses Geist. Keeping the scale consistent makes it easier to maintain hierarchy across different interfaces.

Geistxs · 13 / 16.25
Hxg
Line 16.25Tracking 0.32Regular
4xl€24,18039/48.75
3xlGood morning31/38.75
2xlOctober invoices24/30
xlOverdue this month20/25
lgHarbour & Co18/22.5
baseSend a reminder16/20
smDue in 14 days14/17.5
xsWe only use it for invoices.13/16.25
xxsUpdated 2 minutes ago11/13.75
Weight
Line height is always 1.25 and letter-spacing 0.32px. Point at a size to see its line box, and the guides measure at that size.

Buttons

Buttons share the same label styling, with size variations handled through padding and height. Icons use a consistent 16px size and sit 6px from the label.

Each variant defines its own dimensions, border, radius and text colour. These rules keep buttons consistent wherever they're used.

—

Hover any part of the button to measure it.

Inputs

Fields follow a shared structure: a label, an input and optional supporting text. The spacing between these elements stays consistent, and the border changes to reflect hover and error states.

Keeping the label, field and help text together also makes the component easy to reuse across forms.

We only use it for invoices.

—

A field is a label, the input and a line of help, 8px apart.

Sidebar

The sidebar sits directly on the page canvas, with a subtle fill to indicate the selected item. Projects can expand to reveal their pages, with indentation showing the hierarchy.

The component handles the navigation structure and selected state, while the content can change between projects.

—

The selected row gets a 5% wash. Projects fold open to their pages, indented to line up with the name.

Bottom bar

Several of my interfaces use a floating bar at the bottom of the page, with page sections on one side and the main action on the other.

The component defines the layout, spacing, border and shadow. Its appearance can vary by theme, including the corner radius and treatment of the active item.

—

The bar at the bottom of a page, with its main action beside it. Eyes draws it as a pill, the older products with 10px corners.

Corners that nest

The radius scale defines how rounded different elements should be, from larger cards to smaller controls and chips. Nested elements use smaller radii so their corners sit neatly within their containers.

For example, a segmented control has a 2px inset, with the selected segment's corners following the shape of the outer track.

—

A 2px inset, so the segment's radius sits 2px inside the track's.

Cards share the page colour and use a subtle border to define their edges. This keeps the interface restrained while giving different elements enough separation.

Paid on time

81%

+4%

—

Cards share the page colour. Only the hairline sets them apart.

Layout

Pages use a twelve-column grid with 16px gutters. Form sections can place a heading alongside their fields, with consistent spacing between the two.

Shared spacing rules also apply to component padding and the gaps between elements. This makes it easier to build new screens without having to work out every measurement from scratch.

ProfileThe details clients see on your invoices.

You can't change this later.

—

A form section on a twelve-column grid: the heading spans half, the fields six columns each.

One system, six products

I've used this system across six products, each with its own visual identity. Themes control the colour palette, typeface, corner radii and selected states. The older products use Inter, smaller corners and a raised white selection, while the analytics dashboard uses Geist and a darker active state.

October invoices

Invoiced

€24,180

+12%

Paid on time

81%

+4%

Overdue

€3,420

-6%
ClientStatusAmount
Harbour & CoPaid€4,500.00
Lindqvist StudioPending€1,250.00
Okafor LabsDraft€980.00
Demo

The demo above lets you switch between themes, adjust settings and inspect individual components. You can also explore the colour tokens and see where they're used throughout the interface.

The components are built with Radix primitives and Tailwind, with design tokens controlling the shared styling.

– Joan