Almenr Design System

Almenr Design System

When I joined Almenr, there was no design system in place, resulting in inconsistent UI and a recurring need to consult design on decisions that should have been self-evident. I built a system incrementally, growing it to around 30 components shared across five teams.

Role

UI design

Design systems

Front-end development

Year

2021-2025

Client

Almenr

When I started at Almenr in 2021, there was a lack of visual consistency in the UI and design artefacts. Design would often get butchered in development. I realized that something could be done to mitigate this, while also building the tools for myself to speed up mockups and prototyping.

DurationOngoing, ~1 year
Results~30 components adopted across the product

Redesigning the foundations in Figma

Process

Starting in Figma, I redesigned the primitives, defined our brand colours and added tokens. At the time, Figma was less advanced than it is now: reusable components existed, but variables did not.

Button documentation in Figma
Component anatomy

I investigated accessible colour contrasts and best practices for different components by studying other systems, such as MUI, IBM's Carbon and even Old Apple HMI guidelines.

Sample of Figma documentation

Building strong foundations in code

Decision

The design system grew slowly, starting in Figma and mainly serving design. The open question was how to build strong foundations in code.

ShadCN came along in 2023 which made it possible to simply copy existing components and build on top of them, using a simple API structure and Radix accessibility standards built-in, as well as compability with Tailwind and Typscript, which was part of our stack. This made it a easier pick than something like Carbon, which offered less flexibility and ownership, as well as a large API surface area. Chakra UI lacked some important components like Search/Dropdown.

We preferred the classNames-approach instead of the chakra prop styling. Besides, we were looking for something in the long run, without framework constraints and optimal performance.

Learning by doing

Outcome
Components, preview

Building a design system was a lot of learning by doing, and something I worked on incrementally. It grew to almost 30 components, including documentation.