In what way is JS any more maintainable than CSS? How does writing CSS in JS make it any more maintainable?
So the big deal about css-in-js (cij) is selectors. The biggest win from cij is that computers generate selectors for you automatically. While strategies like oocss, etc are conceptually great, relying on selectors to enforce those architectures are hard in a global namespace because there is always a chance of a clash; if not now, 3 years in the future when the team has changed and become bigger and whatnot. This is exacerbated with third party libraries.
Keep Math in the CSS
There is a sentiment that leaving math calculations in your CSS is a good idea that I agree with. This is for math that you could calculate at authoring time, but specifically chose not to.
Researching a Property in the CSS Specifications
Rachel Andrew shows us which direction is up on a gift that looks great but comes with complex instructions. Like most operating manuals CSS specifications can seem overwhelming, but it turns out that some of the most daunting tasks can be simple when you know what you’re doing.
An Introduction and Guide to the CSS Object Model (CSSOM)
There's another object model you might want to become more familiar with: The CSS Object Model (CSSOM). Likely you've already used it but didn't necessarily realize it. In this guide, I'm going to go through many of the most important features of the CSSOM, starting with stuff that's more commonly known, then moving on to some more obscure, but practical, features.
CSS-in-JS or CSS-and-JS
Tired of all the arguing, John Polacek build a demo showing you can build the same things using CSS-in-JS or traditional CSS & JS techniques.
CSS at the Intersection, by Natalya Shelburne
CSS exists at an intersection between mental models. How do we know? Because we keep hearing the same endless debate: "Is CSS broken or awesome?" Instead, we should work on building tools for collaboration - enabling teams to communicate by creating interfaces to accommodate different mental models.