04 · Living design system

My résumé, as a system.

This whole site runs on one small set of tokens, type, and motion. Here it is, taken apart — the way I'd document a system for a team to build on.

Color

Ground

#f3efe6

Surface

#fbf9f4

Border

#e4ddce

Clay

#cc785c

Clay deep

#b15c3d

Ink

#1b1813

Muted

#6c6555

Type

Display / Newsreader

The whole surface.

Heading / Newsreader

Design and build are one job.

Body / Inter

I own the type, the motion, the components, and the deploy that ships it.

Mono / JetBrains Mono

const craft = attention.to(details);

Components

Tag

Avatar chip

inline code

Motion — hover a tile

…and the résumé is just data

:root {
  --name:    "Clayton Young";
  --role:    "Design Engineer, Web";
  --origin:  "the trades" → self-taught;
  --shipped: 2 products, 1 paying customer;
  --stack:   React, Next.js, TypeScript;
  --status:  available;                /* open to relocate anywhere */
}

A system is only worth it if a team can build on it. That's the job.

claytonryanyoung@gmail.com