Website audit and component system refactor

A demo built for a specific brief. Not client work: the material shown is placeholder content.

I made a refactor demo for a four-page marketing site that had grown one-off by one-off. An audit reads the site's code export and measures it; the same audit runs on the old and rebuilt sites, so every figure is measured. Before: 185 classes defined, 22 unused, 38 auto-named, 95 used only once, 58 duplicate rule blocks, 26 distinct colors in 6 near-duplicate groups, 19 font sizes, 24 spacing values, 14 !important flags, 5 inline styles, 12,823 stylesheet bytes. After: 60 classes, 0 unused, 9 colors, 7 font sizes, 8 spacing values, no !important or inline styles, 5,540 bytes. The rebuild uses 19 variables, Client-First utilities, block_element component classes and is-* combos, and ten section components by Relume category. A migration map sends every old class to its replacement or removal, a composer builds new pages with zero new classes, and a variables panel shows one token change reaching every page.