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

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.

AUDIT
Uncovering 124 component sets across 7 breakpoints.
Auditing the file revealed widespread duplication across layouts and screen widths:
01

02

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

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.

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.

VARIANTS IN PRACTICE

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.
Usage rules and responsive breakpoints documented for the team.

Reusable Figma component linked to semantic color variables.

CSS media queries referencing shared token names and specs.

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.

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.