Andria,
Well, it just struck me as unnecessarily confusing to require designers, reporters and copy editors to learn and use two different editing and layout systems. Also, to anwer Kilometer, we haven't tested the InDesign-InCopy piece, just seen demos.
dan _________________ SND Boston
October 11-23, 2007
http://www.sndboston.com
To all the newspaper professionals who are giving me their time and patience in this discussion. Invaluable stuff, thanks everyone _________________ originality is core
We're upgrading to 6.12 in the next couple of months and will probably start playing with the InDesign integration. But doesn't seem worth getting serious about till the InCopy part arrives with 6.13/14. And probably a couple of releases after that to get rid of the inevitable bugs.
The way we envision using this is:
a) some of our small "niche" products." Like we do a Link-like weekly called 210SA. It involves a small, very collaborative staff, is very design intensive and is a self-contained product. So it would make a perfect candidate for an all-InDesign CCI product.
b) Certain daily pages or sections -- features fronts mainly -- that those working on them would know the InDesign workflow is coming.
c) Select enterprise packages or centerpieces that we want to give some some extra love to.
d) Charticles and other "ASF" story packages. Now we do them totally outside of CCI, either in InDesign and Freehand, so they're not in the workflow and the copy isn't available to export to archive or online.
It is somewhat of a pain to develop, support and train for two different environments. But I think the desire for InDesign goodness (among designers and even some section editors) is strong enough to put up with the pain. (In theory, anyway: We haven't had to actually deal with the headaches like Boston has. And they've dealt with plenty.) _________________ REMEMBER THE ALAMO ...