Fee-fi-fo-fum—Ligatures and Typekit

Recent viewers may have noticed that Effra, as rendered on this site, had some ugly characteristics (especially fi). At first I had concluded that Effra simply lacked ligatures for the web but a more exhaustive investigation led me to understand that the issue is actually down to Typekit settings. Specifically, all characters need to be selected in the Kit Editor.

Sure enough, once updated (and changes propagated), the text renders tolerably well (at least on the current version of Safari for iOS).

Typekit trauma

I was tweaking the font styles in the Squarespace control panel and noticed that when I selected Typekit fonts they were falling back to the system default Serif font.

Step 1: Check whether the problem is with the domain name

When the Kit was created at Typekit’s website it was registered with koumparos.ca but not the underlying Squarespace name, so when changing the site it is not pulling the Typekit fonts.

Step 2: Add squarespace name to Kit

Go to Typekit.com, log in, select Typekit Editor then Kit Settings.

Add squarespace name to list of domains, and then save.

Wait a few* moments for the changes to propagate.


* Where ‘few’ is defined as ‘more than an impatient person would like’.