My face and words in print
Recently I was contacted to provide a short quote about why CSS preprocessors are awesome. This wasn’t a hard task as I spend a lot of time evangelising the use of preprocessors, specifically Sass.
Preprocessors save you so much time when going from an idea to an implementation, by reducing the amount of code you have to write, and providing some much-needed data-structures and logic to CSS.
I’m not saying a lot there, but given a 30-word restriction, and trying to focus on just one aspect of why CSS preprocessors are awesome, I think I did pretty well.
Anyway, this quote was to be included alongside a “Power up CSS preprocessor” feature written by Richard Wentk that appeared in issue 236 of Web Designer Magazine.
I haven’t bought a magazine in a long time, but to have my words printed is a pretty nice thing, so naturally I bought a physical (and even digital) copy of Web Designer Magazine the moment this issue was published.

Imagine my surprise when I found that my face covers 1/3 of a page at the start of the feature.
The feature is nice, and does cover a lot of the pros/cons and features of various types of CSS preprocessor.
Related posts
- Chasing build speed on Jekyll 4
I’ve been putting off upgrading from Jekyll 3.10. Partly late-adopter habit, partly because my setup worked fine, and a version bump seemed simple enough. I should know better by now. It mostly was.
- Antiquated CSS and why we needed it
I came across a catalogue of antiquated HTML snippets and artefacts, the kind of markup we just accepted as necessary in the <head> of every site. It got me thinking about the CSS side of that same period, the stylesheets rather than the markup. My first job in 2009 was building marketing campaign pages for an electronics distributor’s B2B storefront, where dropping IE6 was not a conversation anyone was going to have. Developers eventually landed on one clean way to target different IE versions, but getting there took a lot of less elegant detours.
- How I'm using CSS View Transitions on this blog
In the old days of the web, animating between pages meant faking it with jQuery. Then came pjax, which used pushState to swap in fetched content and fake a full navigation without one, still relying on popState to stop the back button breaking. Every single-page app since has done some version of the same trick, intercept the link click, fetch the new content, swap it in, animate the swap yourself. It works, but it means every navigation runs through a JS router, even on a static blog that didn’t need one otherwise. Cross-document view transitions do the same job without any of that, and there’s no JavaScript API involved at all. It’s a single @view-transition rule in the CSS. No router, no fetch, no client-side history hijacking, the browser still does a real navigation to a real URL, it just captures the outgoing page as it leaves and lets CSS animate that against the incoming one.
Discussion
No interactions yet
Join the conversation
Reply from your own site with a Webmention (how?).
