Occasionally, I’ll be reading a website and just wish I could use another, better font. I can, of course… I can go look up the element on the page that I want to change, use the developer tools to dynamically alter the page, and go back to my reading. This is a pain in the neck, though, and sometimes I want to use fonts that I don’t necessarily have on my computer – like “Athelas,” the font that Readability uses to display its body text, and which they get using Typekit. Read on, intrepid explorer →

In the last few years, there has been an explosion of development in the HTML and CSS specs, much of it driven by browser innovation. As early as 2007, Apple began pushing out vendor-specific prefixes to support CSS properties not yet in the open specification. Other browser developers have followed suit, so that there are now each of -o (Opera), -ms (IE9+), -moz (Mozilla/Gecko rendering engine), and -webkit (Safari and Chrome). Read on, intrepid explorer →

A few months ago I ran across Chip Cullen’s absolutely fantastic ligatures.js – a very simple jQuery function that manually replaces character pairs or triplets with their corresponding unicode ligature. There was just one problem: to use the function, you had to manually test each of the characters you wanted to use against the target font. This is potentially a lot of work, especially if you have multiple custom fonts on your page. Read on, intrepid explorer →

(A note to would-be designers and developers, and to myself.)

You don’t really know a language till you know the library and the tools. Syntax is easy.

Read on, intrepid explorer →