Search

A lovely overview of much of the new CSS that has landed (or is landing) in browsers recently, and how that relates to component-led …

One of the core downsides to CSS-in-JS is that you have to compile it on the client, which means increased bundle sizes and slower rendering. Linaria is an attempt to fix that, by providing all of …

In which I start off asking a simple question: what content categories should I use on this website? Four hours later, I've discoverd information gardening, now pages, digital-me libraries, and oh so much more. And yes, I think I've answered that first question. Fancy a trip down the rabbit hole?

Jeremy has been updating The Session to use variable font sizes with the new CSS clamp() property. He offers some interesting ideas on how best to do …

The increasing use of React Server Components is meaning the end of the CSS-in-JS era. But what options exist to fill that gap? I've been pleasantly surprised with what I've found.

I'm still enjoying the wombo-combo of Sass and CSS Modules, but my React-ified brain occasionally blanks on how to approach certain problems. The one that catches me out the most: style inheritance.

Using pseudo-selectors like :where and :not to invert style rules, allowing for better code encapsulation and context sharing across a codebase.

2023 was another BIG year in terms of, well, everything. We travelled all over the world. We attended scores of major events. And we got married. It's taken a while to write up, as a result!

Every now and then someone writes a really entertaining and/or interesting critique of the whole modern web ecosystem thing that we are stuck using. This is one of those posts. I don't agree with it …

I've long "known" that if you set list-style: none on a <ul> or <ol>, then you "should" add role="list" to that element as well. If you don't, Safari/VoiceOver will ignore the inherent …