
Why CSS Utilities Clobber Each Other — And How @property + :where() Fixes Composition Forever
If you have ever built a CSS utility library, a design system, or even a small set of helper classes,...
Tag archive

If you have ever built a CSS utility library, a design system, or even a small set of helper classes,...

WovenUI started as an SCSS framework: readable utility classes, an apply() mixin that takes any...

Originally published on LinkedIn. I'm gradually migrating my LinkedIn articles over to DEV — this is...

WovenUI does something most CSS frameworks avoid: its apply() mixin reads a list of utility items,...

In April 2025 we introduced NuvoUI, an SCSS framework built around readable class names and an...
CSS has been around for about 30 years. It is the only styling language built specifically for the...

Why BEM? As frontend projects grow, CSS quickly turns fragile—poor class names cause style...
In today's software development, software development is a smart job. Software development not only...
How color-function-notation silently rewrote rgba() to rgb() across our codebase — and three ways to fix it.
I saw Apple's iPhone page in 2016, thought 'I can build that in jQuery,' and somehow I'm still maintaining it in 2026. Zero stars. Zero regrets.

What I learned leading 4 markup developers: agreements die, linters don't. Variables for everything, typography as data, spacing tokens, and the mixin trick nobody talks about.

What native CSS can do today, what's coming in spec, where SCSS still wins — and the risks nobody mentions before switching. A honest breakdown for teams thinking about dropping the preprocessor.