I chose that particular font to check whether I could get Typekit working here at WordPress.com. It’s hardly a subtle change from Tahoma, the main heading font for this blog, and it looks nothing like Georgia, the workhouse here. For this testing, I wanted an intrusive font, and was amused when I found one appropriate in name as well as in appearance.
Typekit has since arrived at WordPress.com, but doesn’t require the CSS upgrade. Well, in a way it does. Consider the following barriers to changing the CSS on a WordPress.com blog: (1) it costs money; (2) it requires knowledge of CSS; (3) it requires knowledge of the way CSS is used in the blog’s particular theme.
I find the third and last of these barriers to be the highest. What heading level does a WordPress theme use for the blog title? for the tagline? for the post title? for headings in the sidebar? And what other selectors (besides h1, h2, etc.) are used, and how are they used? The answer varies between themes.
The theme I’m currently using, Simpla, uses h1 for the blog title. So to test Typekit, I used its kit editor to associate h1 with the distinctive Intruder Alert. That font was for some reason applied to the blog’s tagline (rather than to its title).
I emailed Typekit support over the weekend, and today received a response. I needed to use the selector #header h1. At a more general level, I need to be aware of CSS selector specificity.
My point, and I do have one, and I am getting to it, is similar to this one. Getting TypeKit to work on your blog can be frustrating especially if you are not familiar with CSS. That’s a quote from (and a link to) a guide to using Typekit at WordPress.com. The guide is good, but the quote could be more specific. You need to be familiar with the CSS of the theme.
My CSS isn’t terrible. I’ve tweaked a few themes, including Simpla for this blog. I found Typekit it harder to apply Typekit to that CSS than I did to tune the CSS itself.
I suspect that using Typekit is trickier than editing CSS. I’m generalizing, not only from my own experience, but from what others have written (in, for example, a post in the WordPress.com forums).
So, although Typekit has lower financial barriers to use than the CSS upgrade, it has higher overall barriers to use. I have concerns about this. One is that it’ll cause frustration for WordPress.com bloggers who see that they can try Typekit for free. The other is that Typekit support may be swamped. Anyway, time to email thanks to the Typekitter who supported me.