Website Design System

A responsive website design system for a nonprofit organization, featuring reusable components, shared design standards, and developer documentation.

Design Systems · Responsive Design · Developer Handoff

Data Science Alliance website hero built from the design system

CHALLENGE

Updating the growing site became slow and error-prone.

The original library was built to launch fast, so simple updates meant manual edits across disconnected layouts, which caused visual drift and pulled design out of sync with code.

ROLE

UI/UX designer

TOOLS

Figma, GitHub, Google Docs

IMPACT

Cut components from 124 to 11 and tokenized 144 variables for faster dev handoff.

The original Figma file with page frames for home, careers, about us, our work, events, donate and projects at every breakpoint

AUDIT

Uncovering 124 component sets across 7 breakpoints.

Auditing the file revealed widespread duplication across layouts and screen widths:

01

Disconnected component sets.

Disconnected component sets.

Updating shared styles required manual edits across duplicates, causing visual drift.

Updating shared styles required manual edits across duplicates, causing visual drift.

Three outline button components, default, large and small, each built as a separate component set

02

Rigid layout structures.

Rigid layout structures.

Designers had to detach instances or rebuild assets whenever layouts needed to flip.

Designers had to detach instances or rebuild assets whenever layouts needed to flip.

Two image and title layouts, v1 with the image on the left and v2 with the image on the right, built as separate component sets

03

Mixed legacy and current assets.

Mixed legacy and current assets.

Keeping outdated components in the library made it unclear which version to pull.

Two navigation bar components, Main Nav and Main Nav updated, both still in the library

FOUNDATIONS

Design tokens became the shared foundation.

We organized colors, typography, and spacing into 144 Figma variables across Primitives, Theme, and Responsive collections to enable global style updates.

Figma variables panel with Primitives, Responsive and Theme collections, showing Theme text tokens mapped to color primitives

COMPONENT ARCHITECTURE

Applying properties to make components flexible.

Using variants, editable properties, and nested instances allowed designers to swap content and layouts without detaching components, cutting navigation variants from 44 down to 6 responsive layouts.

The Join our community card before and after the refactor, with the refactored version controlled by layout, content and button properties

VARIANTS IN PRACTICE

Event cards built from one component with the image on the left and on the right, plus a stat card variant

DOCUMENTATION & ENGINEERING HANDOFF

Bridging design tokens and documentation with production code.

I co-authored a spec guide defining usage rules and breakpoint behavior, aligning Figma tokens directly with engineering's CSS stylesheets.

Spec

Spec

Usage rules and responsive breakpoints documented for the team.

Two image and title layouts, v1 with the image on the left and v2 with the image on the right, built as separate component sets

Tokens

Tokens

Reusable Figma component linked to semantic color variables.

Two image and title layouts, v1 with the image on the left and v2 with the image on the right, built as separate component sets

Code

Code

CSS media queries referencing shared token names and specs.

Two image and title layouts, v1 with the image on the left and v2 with the image on the right, built as separate component sets

RESULTS

From 124 disconnected sets to 11 governed building blocks.

The refactored library condensed 124 legacy sets into 11 flexible components and 73 variants, reducing visual drift and supporting a 4-breakpoint redesign.

Treemap of the refactored library's 11 components sized by variant count, led by Button with 28 and Nav link with 10

The refactored library includes 11 reusable components and 73 variants. Each rectangle represents a component, sized by its number of variants.

REFLECTION

Designing for the people who maintain the system.

Deciding what should be a variant and what should be an editable property, and documenting why, showed me that architecture choices matter most to the designers and developers who use the library every day.