Reconsidering Typekit as a sustainable solution

tk-logoypography is an important aspect of web design. Some time ago, we rediscovered the joy of real fonts for web thanks to Typekit. It has been made a huge buzz around this web service because the way it works was really new. We got many promises.

Web fonts aren’t actually new, as Internet Explorer was able to handle @font-face since its early versions. But we never had a so easy solution to implement them in the code of the websites we build. We previously had to buy licenses for each font, convert them for each browser (if the corresponding files were not provided) and insert them in the CSS. Now with Typekit, we just have to browse the huge fonts library, to add the font(s) to a kit and to copy/paste a JS snippet. We especially like the fact that we just have to add/remove fonts to/from a kit in order to make live changes to the website. No uploads, no big CSS changes. Plus, Typekit guarantees that you respect the foundries’ licenses (remember that with a normal @font-face embedding, everyone can find and download the fonts in use).

First I was using the free (and limited) plan from Typekit. After that, I considered to opt for a paid account in. I was really happy to be able to add custom fonts to any website, if and when necessary.

But there is one major disadvantage in using Typekit. Your website do rely on an external service.

Typekit is now more reliable.

93d65656929f1f13d16d03b687670a32SSSSSSSSSSSSS