All cases

Kerozene

The studio's design system

One system behind everything Kerozene designs: tokens, components and documentation, shared by every application, the website among them.

Design systemFigmaTokensDocumentation
Client
Kerozene
Scope
Design system, tokens & component library
In use
Every studio application, including kerozene.ch
Built with
Figma, with code syntax for Tailwind CSS
The brief

One brand, many applications

A brand that lives across several applications cannot rely on everyone remembering the same decisions. Without a shared system, every new screen starts from scratch and drifts a little further from the last. Kerozene needed a single source for every decision, readable by designers and developers alike.

  • 01Several applications, one visual language
  • 02Two grounds, dark and cream, that have to hold together everywhere
  • 03Decisions readable by designers and developers alike
The semantic tokens of the Kerozene design system in perspective: the same panel in Ink mode and in Paper mode
The approach

Tokens first, and everything built from them

Every colour, spacing step, radius, shadow and text style is a named token, and every component is assembled from those tokens alone. Each token carries its equivalent in code, so what a designer picks in Figma is exactly what a developer writes.

  • Named tokens

    Colour, spacing, radius and type as variables, each with its equivalent in code.

  • Two modes, one component

    Ink and Paper: placed on either ground, a component adapts its copy and borders on its own.

  • Built from instances

    Larger components are made of smaller ones, so a change travels everywhere they are used.

  • Documented in context

    Every token and component shown on the ground and in the use it was designed for.

The work
01

Foundations

Colour, typography, spacing, radius, elevation and brand, as variables and styles. Semantic tokens point to the base palette, so switching a frame from Ink to Paper changes every colour inside it at once, without redrawing anything.

The Color page of the Kerozene design system: the semantic tokens side by side in Ink mode and in Paper mode
The Typography page: the Poppins specimen and the type scale, each style with its Tailwind class
02

Spacing

A 4px base shared with the code, in fifteen steps: the small ones build components, the large ones separate sections. Every bar on the page is bound to its variable, so changing a token redraws the documentation as well.

The Spacing page: fifteen steps on a 4px base, each bar bound to its variable
03

The logo as a component

Tagline, wordmark and mark are three variants of one component. The letters and the flame keep the logo reds on every ground, while the tagline follows the copy colour, so a single instance reads on Ink and on Paper alike.

The Brand page: the Kerozene logo in its tagline, wordmark and mark variants, each on Ink and on Paper
04

Components

A complete library, from the smallest atom to whole sections: icons, buttons, tags, avatars, form fields, navigation, service, case and testimonial cards, stat tiles, accordions, headers and footers. Each comes with its variants and states, and each is built from the same tokens, so the light and the dark version of a component are one and the same, placed on two grounds.

The Button page: four variants across default, hover and disabled states, on Ink and on Paper
The Icons page of the Kerozene design system in perspective: thirty Lucide icons