Celestial

Celestial is a design system created to power three products under the same company.

Domain

Design systems

Responsibilities

Design System
Wireframing
Branding

Team

Mentor, for feedback

Overview

Systemising from the start

Systemise from the start

A transparent optimisation process

I learned new principles and processes for building robust design systems during Dribbble's Scaling Design Systems course. I applied these skills by creating my own system called Celestial, used to power three different products for IPTS (the fictional Inter Planetary Travel Syndicate).

My goal was to systemise smart and early, to focus on crafting a process that would allow me to iterate on the products using a coherent and consistent set of rules and tools.

Ideate

Drafting the products

ChatGPT helped me kickstart the product design process, and Midjourney gave me some beautiful inter-planetary imagery.

I wireframed all products simultaneously, to identify where components could be re-purposed, and come up with consistent UX patterns.

IPTS Org, IPTS Travel, and IPTS Rail drafts
Prototype

Designing the system

Once the functionality was decided, and the styling about half-decided, I switched my focus on how the system behind all this would be structured.

I had run into issues in my experience with systems that I wanted to put to the test here. Systemic colours, naming conventions, and tokens especially.

Design tokens
Systemise

Colour as a scalable system

Once I picked my primary and secondary brand colours, along with complementary neutrals to go with them, I used this colour shades generator to complete the palette. I manually adjusted these to ensure contrasts abide by WCAG AA standards.

The matrix of darken and lighten, by increments of 30, gave me some space to add styles in-between when I needed to. The "darken" and "lighten" nomenclature gave me most room to play with from the Design panel.

Contrast-checked colour scale
Systemise

Core tokens

The Tokens Studio plugin enabled me to use these as core tokens, so I could experiment by nesting them within semantic tokens. Sadly for me, this project was done just weeks before Figma's big variable update.

If the primary hue needs to change, all my primary buttons and their states inherit the new colour in the right shade or tint, without the need to change the tokens - only the core, which is used across multiple tokens.

Semantic tokens inheriting core token values
Systemise

Naming is structuring

Researching other teams’ naming conventions showed they are a product of discussion, a crowd-sourced set of decisions. “For this button label, should we use $text- or $button-?” or “Should we go global or semantic here?”. The team decides based on its own average mental model, then tests with external users. For Celestial, I kept all prefixes to indicate the element this token is for, avoiding --c-button-primary-text, but using the infix --c-text-on-primary instead.

I decided on semantic naming due to the simplicity of the products, conscious that some duplication is a downside, and ease of use a great advantage.

Team communication and testing is key to know whether this is usable at scale. For the time being, I especially leaned on Lukas Opperman's article Naming Design Tokens in UX Collective.

All text tokens show “text” as a prefix
Systemise

Base vs. published components

To make it as efficient as possible to update the structure of components globally, I used a root “base” component nested within each published component. These are hidden when publishing the library.

All 96 buttons could be updated by modifying 3 base components. All structural tokens are applied to the base component, while all colour tokens are applied to the published component.

The published button component coming from 3 hidden base components
Systemise

Discoverability
> Usability

The drawback of the base component is more clicks for the user of the system. When updating properties on the Design panel, there are two sets of properties: one on the component (component’s state, e.g. hovered), and one on the base component (component’s content, e.g. image instance).

To compensate for the dip in usability, I augmented the component’s discoverability. I created a component set for each variant so they are not hidden behind a property.

All card types are accessible directly from the panel
Implement

The fast & satisfying bit

Finalising an interface by drag & dropping 80+% of its content is a delicious experience. Creative processes often get stretched between big picture and rethinking atoms. When the system is backed by foundational principles, the designer becomes more confident in focusing on innovation.

Being the creator and the user of the system got me to freely iterate on some choices, making me long for a team to dialogue and compromise with. But it got me to answer my own Why’s behind design decisions authentically.

Final products
Test

Validating by rebranding

Updating the primary font and adding a secondary font meant a rethink in the typography system, but thanks to the --c-font-family- token, it was quick. The new brand colours only had me update the core tokens, which my semantic tokens and components inherited.

The rebrand revealed some detached elements, and the overlooked application of core tokens directly to components. On complex product suites, these accidental shortcuts can lead to exponential decrease of system adoption.

I published a detailed guide for others to replicate these screens using Celestial on Zeroheight.

Rebranded products

sarhowww@gmail.com

LinkedIn

Back to the top