My apologies for the adobe cheap shot, I should have bit my tongue there:).

If it was built into the core systems, that would be interesting, but I could see it as a hell of an OS-font level conflict. We shall see!

Ah, I see where you’re coming from now. I do agree with what you say in the context of Dreamweaver. Developers shoud learn to code manually instead of using WYSIWYG editors and whatnot.

I was alluding to the integration of webfonts in *design software*, i.e. Photoshop or Fireworks. I imagine Adobe will be offering cloud software in which webfonts are available for website design/mockups. That would, IMO, be very useful, also for experiencend devs (or, indeed, Art Directors).

There are probably many problems to be solved, both on the technical and the licensing front, but my point is: if it’s ever going to happen, this is the first step.

For the record: I’m not an Adobe employee — ouch! 😉

Thank you Mandy, but no need for reassurance. I remember your original post, and my original comment thanking you for keeping Typekit still in standalone. My response was to rogier83R from Adobe mentioning the ‘better integration’. For entry level users, I’m sure it will be.

Brady,

As was made clear in the post, Typekit will remain a standalone product. That means you can maintain the same Typekit account you have today. You will not be required to move to Creative Cloud, nor will you be required to use Typekit with any other application.

We have in the past integrated with other services (e.g., About.me, WordPress.com, Behance ProSite), and will continue to do so, while also maintaining the core experience that you’ve come to expect from us. We handcode our sites, too, and no one loves semantic markup more than this team. Rest assured that as we work to make beautiful typography accessible to more people, we also remain committed to users like yourself.

Says the anonymous poster…

While I’d say ‘crap’ is too vague, bloat it is. For those of you not coding with semantic, balanced code, Typekit integration with Dreamweaver should be a blessing for you. To the rest of us who already know we can integrate Typekit on a local or developer server without need of such cruft, it’s just extra layers of marketing and pomp we don’t need. It serves little purpose save an extra layer of integration that helps those who can’t code with a built in option of selection.

OK, maybe I’d like you to add one thing: HF&J fonts.

This is just a regular Typekit account — exactly the same as a Portfolio plan today. We are working hard at deeper integrations with other Adobe applications, but you’ll need to wait a bit for news on that.