This is a wonderful interactive explanation of the way CSS hierarchy works—beautiful!
Jemima runs through just some of the exciting new additions to CSS:
Replacing 150+ lines of JavaScript with just a few CSS features is genuinely wild. We’re able to achieve the same amount of complexity that we’ve always had, but now it’s a lot less work to do so.
And Jemima will be opening the show at Web Day Out in Brighton on the 12th of March if you want to hear more of this!
This is clever, and seems obvious in hindsight: use an anonymous @layer for your CSS reset rules!
Here’s a handy little tool for generating CSS with :has() selectors in order to do quantity queries.
This is a really thoughtful look at the evolution of CSS and the ever-present need to balance power with learnability.
Anselm isn’t talking about becoming a CSS wizard, but simply having an understanding of what CSS can do. I have had similar experiences to this:
In the past years I had various situations where TypeScript developers (they called themselves) approached me and asked whether I could help them out with CSS. I expected to solve a complex problem but for me — knowing CSS very well — it was always a simple, straightforward solution or code snippet.
Let’s face it, “full stack” usually means “JavaScript”—HTML and CSS aren’t considered worthy of consideration. Their loss.
Some styles I re-use when I’m programming with CSS.
If you’re going to toggle the display of content with CSS, make sure the more complex selector does the hiding, not the showing.
I never would’ve known about the `display-mode` media feature if I hadn’t been writing about it.
CSS logical properties here, they just aren’t evenly distributed yet.
An exception to my general rule that ARIA attributes should be added with JavaScript.