Sarah Dayan

Writing CSS that scales is notoriously hard, even when you’re great at it. It often starts well, when you’re crafting the foundations have full control. But soon, unforeseen requests start arriving, the layout you’ve built is being moved around, and you have to undo most of what you’ve done. Soon, you realize that your component-based architecture isn’t as resilient as you thought, and it feels like the best thing you can do is to start over.

Yet, there’s one methodology that’s specially made for change, because instead of being tied to your project, it’s tied to your style guide. This methodology is called utility-first CSS.