This has been talked about quite a bit recently and this is a post that I have been meaning to post, but I have been busy testing…alas.

Custom Fonts

We are currently testing the Typekit offering and simply buying fonts from FontShop and using the @font-face (see Implementations) declaration in CSS. Both are quite nice, although if you have a budget I would naturally gravitate towards buying the Web Fonts and using the @font-face thingy.

Pros: SEO, Make your creative director happy, your users experience something fresh, and your front-end developer easily maintain changes to content.
Cons: You have to load this .js in order for the fonts to show up. IE8 sucks still / .js support could be turned off (not a biggie) / the .js files could be an adherence to bandwidth considerations.
Alternatives: Buy/license the fonts from FontShop, load them on your server and use the @font-face. Don’t forget to write special CSS for Firefox, Chrome and IE.

Worthy Custom Font Comparisons

FontSquirrel vs. Typekit: http://wynnnetherland.com/blog/font-face-off-typekit-vs-font-squirrel
Cufon vs. @font-face vs. Typekit: http://helloschema.com/code/testing-cufon-font-face-and-typekit

Resources:

http://blog.typekit.com/2009/05/27/introducing-typekit/

Huh?: Describes the advantage of using Typekit

http://thinkvitamin.com/design/fonts/getting-started-with-typekit/

A step-by-step process of signing up and using