Stop assuming frameworks solved the cascade. Learn how specificity and source order still rule UI libraries so you can build true CSS architecture.
Also available in Español
The Problem
"We don't have CSS problems, we use Tailwind." "Bootstrap handles that for us." Some version of that sentence gets said on nearly every team that's adopted a framework, and it's usually said with real relief.
It's also not quite true. Frameworks solved real problems. The cascade was never one of them.
Why the Problem Exists
We have utility libraries, class-naming conventions, and methodologies dressed up in framework...
CSS has always had a clear purpose: describe how a document looks, not what it contains. Somewhere...
Here's the take: if you're reaching for a CSS framework in 2026 out of habit rather than a specific,...
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…
Recently, I realized that standard CSS has evolved quite a lot. When I talk with other engineers, it...
