Why most CSS resets bundle opinions with browser fixes—and why quell separates normalization from design decisions.
Also available in Español
The Problem
Every new project starts the same way.
A reset goes in first. Eric Meyer's, normalize.css, one of the modern reset gists passed around in a team's starter template - it doesn't matter which. It happens before the first component, before the first token, before anyone has made a single real decision about how the site should look.
It feels like housekeeping. Not a decision. Just clearing the ground before the real work starts.
If you're starting a web project, you're probably starting with a CSS reset, and for most of us, that...
Specificity issues aren't a discipline failure—they're an architectural flaw. Here is why your clean CSS inevitably drifts into…
A practical guide to building CSS architectures that survive real projects, team handoffs, and the inevitable "can we just change…
One of the easiest traps to fall into when building a design system is accidentally recreating...
CSS rewards addition and punishes subtraction. Here is why every large stylesheet eventually turns into an unmaintainable,…
CSS has always had a clear purpose: describe how a document looks, not what it contains. Somewhere...
