All posts tagged ‘Typekit’

Adobe, Google Partner for Edge Web Fonts

Adobe Edge Web Fonts service. Image: Screenshot/Webmonkey.

As part of its new Edge Suite of tools for web developers Adobe has announced Edge Web Fonts, a new free service much like Google Web Fonts.

In fact Adobe has partnered with Google to make most of Google’s open source fonts available through Edge Web Fonts as well. Both services also include the Source Sans Pro open source font family Adobe released earlier this year and the brand-new Source Code Pro.

The full list of fonts available through the service can be found on Adobe’s new Edge Fonts site, though sadly there’s no way to preview them. Previews of what Adobe’s Typekit blog calls the “more popular” options can be found on the Edge Web Fonts page.

Adobe also plans to work with Google to improve many of the fonts, adding hinting for better rendering at smaller sizes and optimizing other aspects for better-looking, better-performing fonts. The company plans to open source its improvements so even if you prefer to stick with Google Web Fonts you’ll still eventually have access to better looking fonts.

So why go with Adobe’s new Edge Fonts over Google’s existing service? There’s really no advantage if you’re already happy with Google’s offering, especially if you’re downloading Google’s fonts and serving them yourself, since that eliminates the chance that Adobe’s (or Google’s) servers will go down and take your fonts with them. Of course Edge Fonts is powered by Typekit, which has proved itself reliable over the years.

For more info on Adobe Edge Web Fonts head on over to the Typekit Blog, or check out the sample code to take them for a spin on your site today.

[Update: Developer Tony Stuck has put together a very nice preview page of the Adobe Edge Fonts for those that would like to actually see the fonts before diving in, which, presumably, is everyone.]

Adobe Acquires Typekit Web-Font Service

Adobe has acquired web-font service Typekit. Typekit helped pioneer the use of fancy fonts on the web thanks to its easy-to-use service which takes care of licensing, font loading and cross-browser support. Today all a designer needs to do to add typefaces in their page is drop in a couple lines of Typekit code.

Typekit currently serves over 250,000 sites, including The New York Times and WordPress.com, as well as Webmonkey and Wired.

Writing on the Typekit blog, CEO Jeffrey Veen assured Typekit users that little will change, at least for now. “Typekit will remain a standalone product,” writes Veen, “our team will stay together, and we’re excited to start working on even easier ways to integrate web fonts into your workflow.”

Typekit and Adobe are hardly strangers. The companies previously partnered to bring many of Adobe’s more popular fonts to the web — Adobe Garamond, News Gothic, Myriad, Minion and others are all available through Typekit. It seems likely, now that Typekit is part of Adobe, that the service will add more of the Adobe fontface library in the future.

Potential new fonts won’t, however, do much to assuage the fears of those worried about the future of Typekit under the Adobe umbrella. If the comments on the Typekit blog are any indicator, Typekit users are evenly split — about half of Typekit’s audience seems optimistic about the change and half, well, less so. A common sentiment for the latter group comes from a commenter named Jason who writes, “I am happy to see the Typekit team get a reward for an amazing service, but terrified to see Adobe ruin what they created so lovingly.”

Indeed Adobe has a mixed track record with companies it has acquired, as anyone who relied on Macromedia FreeHand or Director can tell you. Hopefully Typekit will fare better, especially since, small though the company may be, it’s a big part of the reason web fonts have become so popular.

When Typekit first launched in 2009 hardly anyone was using web fonts. Browser support was spotty at best and very few type foundries offered web licenses. Fast forward to today and the landscape has changed remarkably. Now every recent browser release supports CSS 3′s @font-face and Typekit has hundreds of fonts from most of the major type foundries.

Obviously much of that change is due to a combination of effort from browser makers, standards bodies and type foundries, but Typekit played no small part as well, helping to create a demand for high-quality fonts on the web, and then delivering those fonts in a way anyone can use.

See Also:

File Under: Uncategorized

Stop Typekit Fonts From Slowing Down Your Site

That's a fancy-lookin' T you got there.

That’s a fancy-lookin’ T you got there.

Typekit is one of the easiest ways to get fancy fonts working on your website. Just sign up for an account, pick a font and paste a few lines of code into your pages. TypeKit takes care of the rest, ensuring that your fonts load and there’s no unsightly flash of unstyled content (FOUT) or other problems.

There is, however, one possible problem with the default way of embedding Typekit fonts. If the TypeKit code fails to load, it can slow down the rest of your site. Typekit avoids FOUT by pausing your page load for a fraction of a second, but if the Typekit script never finishes loading, that fraction of a second can turn into many seconds. While Typekit has excellent uptime, let’s face it, outages happen, and we understand if you don’t want to hang your own site’s fate on another.

For those worried about depending on Typekit there is a workaround — load Typekit scripts asynchronously. The Typekit blog recently put posted an in-depth look at various way to embed Typekit fonts in your pages, including an asynchronous method which won’t slow down your page should Typekit become temporarily unavailable.

The disadvantage of the asynchronous design pattern that Typekit outlines is that it means a bit of extra code in your pages. Most likely a few more bytes in your HTML isn’t going to cause a significant speed hit, but it is something to keep in mind.

See Also:

Typekit Teams Up With Adobe to Offer More Web Fonts

Typekit, the web service that helps designers use elaborate typefaces in their page designs, is celebrating its one year anniversary with a big announcement: the company has added 16 of Adobe’s popular font families to Typekit’s ever-growing stable of options.

With the addition of Adobe’s fonts to TypeKit’s already large library, designers now have access to popular workhorse fonts like Adobe Garamond, News Gothic, Myriad and Minion, as well as slightly funkier options like Rosewood or Trajan, the “movie font.” These typefaces are heavily used in the print publishing world.

The new Adobe fonts are the original cuts of the typefaces, not reproductions or downgraded web versions of the designs. This means it’s now possible to use them just like you would in print work with the same rendering accuracy and technical detail you’d see on paper. Monday’s development should have a positive impact on the use of fancier fonts on the websites of old-school institutions and larger corporations — companies that have been using Adobe products to build their print materials for years. Now that they have the same level of control over details like kerning pairs and line height on the web, they’ll have an easier time making the jump.

Adobe is a little late to the party — the company is one of the last major font foundries to partner with Typekit — but Typekit President and co-founder Bryan Mason tells Webmonkey that the reason for the delay is a heavy attention to detail.

“Adobe has been working on the hinting and screen rendering of these (and others to follow) for months,” says Mason, “[that] means a character-by-character, weight-by-weight review of each font family.”

Typekit is like a YouTube for fonts. The service lets web developers pick a font from its library, pay a licensing fee to the font creator (though some fonts are free), then use that font across their website. Unlike many fancy type solutions on the web, TypeKit isn’t using any sort of image replacement for rendering fonts, just the standard CSS @font-face declaration with a minimal amount of JavaScript to simplify the process and account for various browser versions. The service is one of the easiest ways for web designers to use creative fonts without sacrificing web standards or violating font licenses — most of the time, it’s just a matter of copying and pasting some code snippets. There are also options specifically designed for easy integration with popular publishing platforms like WordPress. The company also released an API last month, allowing third parties to integrate Typekit font selection into their apps.

If you’d like to try the new fonts on your site, head over to Typekit and log in to your account. The fonts are available for all paid Typekit accounts. If you’re using the limited, free option, you’ll have to settle for Adobe Garamond, the only family that Typekit is giving away.

See Also:

File Under: APIs, Fonts

Typekit Gets an API

Font startup Typekit introduced an API Thursday that lets web programmers generate kits from the Typekit library behind the scenes.

The company has previously only offered the option of picking fonts and generating kits using the web-based tool on its site. But by releasing an API, it’s giving people the option of building Typekit into their own apps or simply extending the way they use the service.

Writing on the Typekit blog, Paul Hammond says: “The Typekit API gives you the ability to programmatically create, modify and publish kits. It also allows them to fetch metadata about all the fonts in the Typekit library.”

Here are the documentation pages. As you can see, the Typekit API returns data in a few different flavors (JSON, XML and YAML)

There’s an example page set up on Github, and while there isn’t much there yet (just a kit generator for Ruby) we can expect more soon.

If you haven’t yet explored Typekit’s service for including fancy fonts in your site designs, you should. Especially handy is the WebFont Loader, an open source library of scripts that Typekit developed to help eliminate the “flash of unstyled text” that happens when a page loads. The WebFont Loader offers a number of JavaScript events which allow developers more control over when and how their fonts are loaded onto the page.

See Also: