Though I have the utmost respect for Massimo Vignelli, and am a fan of his work, his we use too many typefaces is just plain wrong. It’s by no means the first time Vignelli has voiced these views…

For any designer to claim that a half-dozen or a dozen typefaces is enough — well that’s their prerogative. However, it’s one thing to say ‘twelve typefaces is enough for me’, but to claim ‘twelve typefaces is enough’, period; extrapolating a generalisation from a personal imposition is rarely, if ever helpful.

Since typography is one of the most challenging and important aspects of web design, it’s important to have useful tools that can make things easier. Here’s a list of tools that will be a big help in making your typography beautiful, and you won’t even have to leave your browser.

When I first started to design Baseline, I wanted to base the grid on the work of Josef Müller-Brockmann, unfortunately some missing CSS attribute — like type leading — kept me from implementing a true grid based approach. I then decided to look back at the basic grid that is used in print: the baseline grid.

When we started Small Batch Inc. last year, our goal was to explore what’s now possible on the web. That exploration has taken many shapes: bringing together a community at The Start Conference, working with our friends at Twitter for a few months, and digging deep into data with Wikirank. Now we’re focusing on an entirely new idea, and we’d like to share that with you. It’s called Typekit.

We’ve been following developments in web browsers very closely, looking for new and smarter ways to build stuff. Last fall, we started seeing renewed interest in linking to fonts via Cascading Stylesheets. While the W3C working draft has been around for years, a new wave of browser support will finally offer designers more control over fonts on the web. A particularly cogent article from John Allsopp, followed by frequent conversations with him, helped us understand that there was a significant opportunity here.

Looks beautifully simple.