Don’t judge a book by its cover
Some neat CSS from Tess that’s a great example of progressive enhancement; these book covers look good in all browsers, but they look even better in some.
Some thoughts on CSS, media queries, and fluid type prompted by Utopia:
We say CSS is “declarative”, but the more and more I write breakpoints to accommodate all the different ways a design can change across the viewport spectrum, the more I feel like I’m writing imperative code. At what quantity does a set of declarative rules begin to look like imperative instructions?
In contrast, one of the principles of Utopia is to be declarative and “describe what is to be done rather than command how to do it”. This approach declares a set of rules such that you could pick any viewport width and, using a formula, derive what the type size and spacing would be at that size.
Some neat CSS from Tess that’s a great example of progressive enhancement; these book covers look good in all browsers, but they look even better in some.
You might not need (much) JavaScript for these common interface patterns.
While we all love the power and flexibility JS provides, we should also respect it, and our users, by limiting its use to only what it needs to do.
Yes! Client-side JavaScript should do what only client-side JavaScript can do.
Every one of these five proposals is worth a vote.
Mind you, Rich’s cynicism is understandable.
A fantastic explanation of the building blocks of SVG, illustrated—as always—with Josh’s interactive examples.
I should be using the lh and rlh units more enough—they’re supported across the board!
How to make the distance of link underlines proportional to the line height of the text.
Make your links beautiful and accessible.
A redesign with modern CSS.
Having fun with view transitions and scroll-driven animations.
Going back to school in Amsterdam.