🚀 go-pugleaf

If you are researching, it would probably be best to get a trial version of 2.0, which is available from the "downloads" link at <http://www.adobe.com/products/indesign/main.html>

In terms of a web/print workflow, that's all I've been doing since there was a web, so I have some experience. Yes, on the one hand, the tight integration with the other Adobe products makes sense in terms of things like PhotoShop and Illustrator graphics: these can flow both into InDesign and into HTML output quite effectively. However, I don't take InDesign's HTML output seriously, but always look at the flow like:
[Data or XML]-> Web layout (via XSLT or scripting) and
[Data or XML]-> InDesign layout (via scripting)

Graphic objects are maintained as vectors or in a high-resolution raster format, then converted to the ideal format for each type of output.

It might be nice to somehow work with both HTML and print layout in the same place, but I haven't found current tools really ready for this (natural, as the outputs are so different), so I tend to work with very different processes to create distinct streams of output; at least there is a single source for data and a single, highest-resolution source for graphics, which makes it somewhat future-proof. Whenever the web truly supports vector graphics, for example, we can simply change the conversion process for those graphics that are maintained as vectors in their high-resolution state.

Max