Case Study — March4orth Design
A design system business in 6 weeks.
From zero to a live token library, membership product, content pipeline, and revenue infrastructure — built systematically, shipped fast.
From zero to a live token library, membership product, content pipeline, and revenue infrastructure — built systematically, shipped fast.
Most designers learn tokens, type scales, and spacing systems on the job — under pressure, with no framework. The gap between "I know what a design system is" and "I can build and maintain one" is enormous, and almost nobody teaches it directly.
The build was treated like a design system project — tokens first, then components, then the surfaces that use them. Every decision was documented. Every page followed the same token set. The business model was built in parallel, not bolted on after.
The token architecture follows a two-layer model: raw values at the primitive level, intent-named tokens at the semantic level. Every color, size, and spacing decision on every page traces back to the same token file.
The entire site is vanilla HTML and CSS — no build tool, no framework, no component library dependency. The token system is the architecture. GitHub Actions deploys to GoDaddy on every push to main. WordPress handles the blog and auth layer.
Not a side project, not a prototype. A functioning design system product with a membership, a content channel, a blog, and a studio. Every part feeds the next.
