Skip to content
Fundur
T4 · Design systemDesign SystemsPublished 15 days ago

Storefront Tokens

The design system this storefront is built on — tokens, primitives and the reasoning behind each decision.

Opens in
Figma, React, Next.js, Tailwind
Screens
18
Components
41
Dark mode
Included
Accessibility
WCAG AA
The design system this storefront is built on — tokens, primitives and the reasoning behind each decision.

01 / 03

01The problem

A near-monochrome system built on one premise: the work supplies the colour, and the interface supplies nothing but order.

02The brief

A design storefront whose own interface is mediocre cannot sell design. The system had to be evidence of the claim, not merely a container for it — while staying so restrained that it never competes with the work on display.

Who it's forDesign teamsFoundersAgencies
ConstraintsDark mode as a first-class citizen, not a filter. WCAG 2.2 AA throughout. Every token had to survive being handed to a developer with no design context.
03The approach

Start from the constraint rather than the palette: if the product is a gallery wall, the chrome has to disappear. One accent, a neutral ramp, three elevation levels, and a strong typographic hierarchy doing the work that colour usually does.

Reference landscape

  • Radix ColorsRight about scales, more colour than a gallery needs
  • DribbbleRight about grid rhythm, chrome fights the work
  • UI8Right about product-page anatomy, no point of view in the shell
04The insight it turns on

If the interface has an opinion about colour, the work loses.

Every marketplace that skins its own chrome loudly makes its products look worse — the eye reads the accent as part of the artefact. Removing colour from the shell entirely, and spending the whole budget on type and spacing, makes uploaded work look better than it does anywhere else. That is a commercial argument, not an aesthetic one.

05How it was made

Stage by stage

  1. 01

    Map landscape

    Nine reference products assessed for what to take and what to refuse — grid rhythm from one, product-page anatomy from another, licence architecture from a third.

  2. 02

    Gap analysis

    None of the references separate the shell from the work. All of them lose contrast in dark mode at exactly the point the imagery matters most.

  3. 03

    Design system

    Tokens authored as CSS custom properties first, Tailwind theme second, so the system is portable to a codebase that doesn't use Tailwind at all.

  4. 04

    Build-ready front end

    Shipped as the running front end of the storefront, with the token file readable in the delivered source rather than described in a PDF.

06The hard parts

What was difficult

Dark mode inverted the neutral ramp and destroyed the sense of depth borders were carrying.

Borders were re-derived per theme rather than flipped, and elevation was capped at three levels so the system never leans on shadow to say something a border should say.

A monochrome shell risks reading as unfinished rather than restrained.

The typographic scale carries the personality — a high-contrast display face against a neutral UI sans — so the restraint reads as a decision rather than an absence.

07What's inside

Exactly what you get

  • Figma library
  • 41 components
  • Token set (CSS + Tailwind)
  • Light + dark
  • React + Next.js
  • Written guidelines
Version
1.0.0
Formats
Figma, React, Next.js, Tailwind
Screens
18
Components
41
Dark mode
Yes
Prototype
Yes
Accessibility
AA
Figma
2026.2

Dependencies

  • Inter — SIL Open Font Licence — included
  • Tailwind CSS — MIT

Commercial fonts are never redistributed — they are named and linked, with a free equivalent substituted in the delivered files.

08What it changed

The system runs the storefront it was designed for, which is the only test that matters.

Part of a system

The Storefront System