Study
Case Study
Client
hobbs.design

Ground­work

A portfolio that argues for systems should be built like one.

I'd spent years saying I work in systems and build what I design. The site making that case had five years of values typed in by hand. So I rebuilt it in public, starting with the tokens.

Focus
  • Design tokens
  • Component library
Built with
  • HTML
  • CSS
  • Figma variables
Wireframe of a case study page, annotated with the atomic layer and class name of each region: site-nav, page-hero, the twelve-column grid, feature-row, and site-footer.
Where the first rebuild ended up. Every label was a real class at the time.

The old site worked but didn't back up anything I was saying.

Nothing looked broken from the front. Underneath, one red lived in a Sass variable and again as a hex, and a heading still had a style attribute from one afternoon in 2021.

Anyone who opens DevTools sees it, and those are the people I want to work with. For a design systems role, the portfolio is itself a sample of the work.

Diagram comparing one color copied into three files, each spelled differently, against the same color defined once in a token file and referenced by name from three stylesheets.
Three spellings of one red, and nothing in the code saying they were meant to match.

First I had to set some rules about where values live.

Before I touched a page, every value moved into JSON in three layers. Base held the raw values, and only base could. Semantic gave them roles. Component tokens came last, and only for components that needed their own.

Those values live in two Figma files now. A plugin opens a pull request on software, my design system repository, and its build writes the CSS this site loads. Nobody edits that file by hand.

The three token layers, base to semantic to component, compiling into dist/tokens.css, with one red traced across all four and a crossed-out return path from component back to base.
Dependency runs one way. The crossed path isn't allowed.

A design system is an agreement about where decisions live.

The layers turn taste into a rule anyone can check. A raw hex outside software's base values is a bug, and you can search for it. Open DevTools and --color-border-focus resolves through --color-role-light-border-focus and --color-brand-primary-500 to #e12a09, the red of the focus ring.

A gap means a missing role

If a rule needs a value the semantic layer doesn't have, I add the role. A raw value doesn't get in just this once.

Dark mode stopped being a redesign

Every color is a role, so dark mode is a second set of semantic values. No stylesheet changed to add it.

The CSS had to match how the design is built.

The first rebuild followed Atomic Design, with main.css importing each layer in order. Pages now load software's reset, tokens and grid first, then one file per component, then this site's own rules. The Swiss theme loads last so it can override a component token.

The layers of main.css after the first rebuild, listed in import order with their files: tokens, base, atoms, molecules, organisms, layout, utilities, with an arrow showing dependency running one way.
The stylesheet after the first rebuild, in the order it loaded.

Files load in dependency order, so nothing has to fight the cascade.

Each component gets one file, so a navbar problem should be in navbar.css. Deleting a component means deleting a file and a link.

Then I built every page from the same parts.

The markup describes structure, and the stylesheets own every measurement. Spacing sits on multiples of eight, plus 2, 4 and 12.

A case study section drawn on twelve columns: a heading spanning the first eight, supporting paragraphs on a subgrid, a bold statement hung across columns five to twelve, and dashed empty spacer spans.
One section of this page on the grid. The dashed blocks are empty spans that push a block into a later column.

A page built from scratch is a fresh set of decisions.

I kept one thing from the old site, the uneven layout. Headings sit left, body text sits right, and CSS subgrid keeps a block's columns on the page grid. No page has an inline style left.

The header is on every page, so I locked it first. My first pass matched the markup but left the links alone, because links felt like content. Then someone pointed out that a global navigation that changes from page to page isn't global.

Twelve pages had to agree on one answer.

Forcing the links to match turned up two defects. The homepage used fragment links that only worked on the homepage, and it sent Resume to the PDF while eleven pages sent it to resume.html.

Two of my colors had been failing for years.

An audit against WCAG 2.2 caught them. The brand red measured 4.36:1 on the page background, under the 4.5:1 body text needs. Muted text, at 40% black, measured 2.6:1.

I fixed both at the value, not where they were used. Software now checks every color pair a component uses, in every brand and theme, on every pull request.

A contrast spec sheet: the 500 red at 4.36 to 1 failing at body size, the 600 red at 5.9 to 1 passing, 40 percent black at 2.6 to 1 failing, and 60 percent black at 5 to 1 passing.
The four measurements that changed the palette. The failing values survive where they still pass.

Fix it in the value and it can't quietly come back.

A fix applied page by page has a shelf life, because the next person reaches for the red that looks right. As a semantic token, the accessible answer is also the easy one. Focus works the same way. One 2px red ring is defined once, and every page opens with a skip link.

I put each part's name on the part itself.

Every component carries a data-xray attribute with its layer and name, such as organism · navbar. The labels on the drawings above came from those attributes. Because they live on the components, they can't drift into a diagram of how I wish it worked.

Claiming a system and showing one are different jobs.

Most portfolios in this field talk about systems thinking, and almost none let you look. View the source of any page here and the structure is labeled in the markup.

Shipping it took longer than it should have.

The rebuild sat in a v5/ folder while visitors kept getting the old site, until an outside audit pointed it out. I moved v5/ to the root and set up a deploy that copies only what should be served. It never deletes, so old pages stayed on the server until I removed them by hand.

Work that hasn't shipped is work nobody has seen.

I'm leaving this in because it's an easy way for a rebuild to fail. The system was sound for a week before anyone could see it.

What the rebuild bought.

Sixty-five commits over nine days. The site looked about the same afterward, which is right for a structural rebuild. The next change got cheaper.

One place to change a decision

A color, spacing step or type size changes once in Figma, and the pull request rebuilds it for every platform.

Pages got cheap

This page is new markup. Everything else on it was reused.

Accessibility is the default

Contrast, focus and skip links come built in, so a new page gets them without extra work.

The repo is part of the portfolio

The source is public, and the commit messages explain the reasoning.

What this sets up, and what it doesn't.

Some of these are next steps. Some are open problems I'd rather name than hide.

React without a rewrite

Each component already has one markup shape, and only the content changes. Turning them into React components is a translation job.

Deployment is still the weak link

Publishing is still manual. Until it runs on merge, finished work can sit unseen again.

This site still restyles software

components.css overrides some of the shared components it loads, and it has raw values of its own. Both belong in component tokens, and nothing checks for raw values yet.

Next project

Bullhorn's redesigned candidate record and token documentation

01 / 07B2B SaaS • Systems

Bullhorn

A new look for Bullhorn's platform, built from the smallest pieces up.

Bullhorn brought me in for three months to update how its applicant tracking system looked, across the whole platform. The candidate record and the candidate list came first, because recruiters use them most. Once I saw how many components sat under those screens, I proposed a token system, got engineering behind it, and spent the rest of the contract building it.

Focus
  • Design tokens
  • Component library
Scope
  • Full platform
  • 500+ components
Context
  • Three-month contract
  • Via Mondo
View case study: Bullhorn