for Change

The Raisely logo mark centred on radiating rings of purple

Raisely Design System

Turning years of hard-won design and tech debt into a system the whole product team could build with confidence

Role: Design Lead + Frontend Development

Tech: Figma, Tokens Studio, React, Typescript, Tailwind, Radix UI, Storybook

Date: 2024

Main collaborators:
  • Laura Schweiger / Senior Product Designer
  • Brigitte Huynh / Senior Product Designer
  • Jesse Martin / Tech Lead
  • Methias Talamantes / Software Engineer

Background

When I first joined Raisely in 2018, we were a very small team and we had our heads down; focussed on building a ground-breaking product for under-served charities and not-for-profits that desperately needed a better way to fundraise online.

Initially, the product had been relatively easy to maintain. However as the company, customer base, and product grew rapidly, we started to build up considerable design + tech debt.

We needed a system to help us craft a more consistent, accessible and stable product with greater confidence and speed.

An organic grid of different system components centred around a large Raisely icon

Check out some of the components we created — you can switch between light and dark mode! 🌗

An organic grid of different system components centred around a large Raisely icon

Firm foundations

Whilst the landscape and tools to create design systems are ever evolving, we had three guiding principles that helped ensure our system remained the dependable and adaptable cornerstone of our product. These principles reflected our commitment to collaboration, accessibility, and longevity:

  1. Created by everyone

    It was owned by the entire product team and leveraged our broad range of skills and diverse experiences.

  2. Accessible to anyone

    It was never an afterthought; accessibility was baked into the system itself, the design choices we made, and the way we built it.

  3. Built to last

    It was robust and provided a firm foundation, whilst also being flexible enough to adapt and foster creativity.

Composition of two product screenshots, one from the 'Team' page, and the other from the 'Fields' page, demonstrating the versatility of the design system

Our wonderful design system in all its glory

Product dashboard screen showing a break down of an organisation's fundraising in figures and graphs

A sneak peek of the 'Organisation Dashboards' feature

Reducing friction & maximising quality

Designers and engineers bring distinct priorities and strengths to the table, which are vital for creating great products. However, these differences can sometimes lead to friction, miscommunication, and reduced quality and efficiency.

This misalignment might manifest as incorrect colors, spacing, or font sizes in the final product, or components being designed without accounting for technical constraints.

As our design system evolved, we continuously sought ways to improve communication, streamline collaboration, and foster clarity to bridge these gaps effectively.

Clear documentation

We reduced friction through thorough documentation. Once a component was approved, a designer would build it in Figma and add detailed documentation.

The documentation included a description of the component, its anatomy, and detailed different states, responsive behaviour, and interactive behaviour where necessary.

This ensured that components were carefully designed and provided engineers with clear guidance to implement them efficiently and to a high standard.

Figma documentation for the Campaign card and Date range picker components, with annotated anatomy and date formatting rules

Create clarity

Clear communication is paramount to effective collaboration and I’m proud that our product team exemplified great communication.

This was imperative in a global, remote company where you couldn't always jump on a call. It's all about enabling everyone to do their best work.

Our files were always full of discussion and our nifty ❖ Handoff Helper component was a great way to provide extra detail and context for engineers.

A starred campaigns list in Figma with yellow 'Note for engineers' annotations explaining greeting logic and sort order

Revolutionising how we build

With this project, we saw an opportunity to rethink how we built and improve the foundation of our design and development processes. It was the perfect chance to adopt new tools and techniques that would make our workflow more efficient, cohesive, and scalable.

Tailwind & tokens

We transitioned to Tailwind CSS, a move I was hesitant about at first — I've always been passionate about pure CSS. But as we adopted it, I quickly came to appreciate its efficiency & flexibility - now I love it!

To supercharge this transition, we integrated design tokens from Tokens Studio directly into the Tailwind configuration. This seamless integration ensured that our design system was consistent, scalable, and easy to maintain.

Code editor autocompleting Tailwind classes generated from design tokens, beside the matching Accent token set in Figma

It felt like magic!

Radix UI

It's not always about working harder, it's also about working smarter and leveraging existing tools. That’s why we adopted Radix UI's primitive component library.

Their components come with accessibility baked in, giving us a solid foundation to work from. By building on these well-tested primitives, we could focus on customising and enhancing features with confidence, knowing our bases were covered.

A tooltip component in the product, alongside the React code that builds it from Radix UI's Tooltip primitive

It's Storybook time

We fully committed to using Storybook when building our design system components, and it was a game-changer.

Storybook lets you build and view components in isolation, treating each as a “chapter” with its own backstory, configuration, and variations. This focus allowed us to perfect every detail without the distractions of the broader application.

We also integrated it with Chromatic, which allowed us to generate component versions on the fly, enabling designers to review and provide feedback without a dev environment.

This iterative approach helped us catch issues early, refine components upfront, and deliver better products with less friction.

Storybook showing a Typeahead input component with its controls panel and a list of system components

Going the extra mile

In my role, I focused on implementing tools and processes that went beyond the standard workflow to improve efficiency, and ensure seamless integration between design and engineering.

These efforts aimed to bridge the gap between Figma and our codebase, making the handoff process smoother and ensuring consistency across the product.

With this project, I was able to flex those muscles a bit more than normal and try out a few things that I'd never done before:

Figma's Code Connect panel showing the React code for a Graphic icon component selected in a design

Code Connect

Using Figma's Code Connect feature, I added a translation layer between our components in Figma and the code, mapping Figma properties to their code counterparts.

A custom Figma plugin generating Tailwind classes and CSS for a selected button component

Codegen plugin

I developed a custom plugin for Figma that used our custom Tailwind configuration to generate bespoke classes from Figma's generated CSS styles.

Loved by all

Our design system wasn't just a tool, it was a game-changer. But don't just take my word for it:

  1. It enables me to focus on functionality rather than spending time measuring pixels and looking up colours. The DX is superb, and it also allows us to be more confident that we're building a consistent and cohesive product for our users.

    Methias, Frontend engineer

  2. I appreciate the simplicity of having a design language as a company, where the components used in designs and the components when building are identical. It's been refreshing to see how a consistent design language also changes how we as developers can interact with a complex codebase.

    Flynn, Frontend engineer

  3. When you're picking up a new screen to develop you already know which components are used, which ones are already developed, and which ones need to be developed.There is a 1-1 relation with design and engineering and you can see and gauge what the end product looks like even before you start.

    Vish, Frontend engineer

Key takeaway:

Shared ownership fosters understanding, brings clarity, increases adoption, and increases quality.