Wait up... I'm asking about the CCI version using InDesign CS2 called Newsgate....
Jayne:
It may not be coming across clear. Here's the bullet-point version:
* CCI offers two production systems, NewsDesk and the newer NewsGate.
* Both can be used with LayoutChamp, InDesign or both.
* Currently, they support InDesign CS2. CS3 support is expected in maybe November.
* Neither NewsGate nor NewsDesk currently supports a workflow with InDesign that includes full workflow and (more important) accurate H&J. The problem is that MS Word (CCI's text editor) and InDesign don't H&J against each other.
* Next versions of both NewsDesk and NewsGate (6.13 and 6.14) will pair InDesign with InCopy as a text editor. Wa-la, accurate H&J.
Bottom line: InDesign is gaining more integration within CCI, but does not have parity with LayoutChamp in regard to production workflow. (But yes, InDesign blows the doors of LayoutChamp as a design tool.) _________________ REMEMBER THE ALAMO ...
Bumping this and seeking concrete information in Charlotte (CCI version 5.5.5.26):
1. Has anyone worked at a place where editors switched from Word to InCopy? How'd that go?
2. Who's working on Newsgate already and is it wonderful or painful?
3. Has the person who sought information here earlier about using Layoutchamp for magazines gathered further details or experience?
4. Is anyone using InDesign for centerpieces and then using Layoutchamp for the design of the rest of a page and section? Does that work OK or is it a workflow mess? Is it worth using Incopy/InDesign sometimes to solve the hyphenation problems at a cost of a clean workflow?
Thanks for any thoughts...(Martin, I know what you think, and the animations always make me laugh. But others who are working on CCI 6.X please weigh in as well).
Tampa, Orange County and I think Columbus are currently using NewsGate. I've not heard of any experiences.
NYT, Boston and (I think) Oklahoma City are the only CCI papers I know of using the InDesign integration. The InCopy part isn't released yet, so no experiences there.
I know Boston was quite unhappy about the practical aspects of adding InCopy -- another app to support and train users on. Probably the biggest hassle with InCopy will be the loss of all your Visual Basic macros in Word. InCopy has a healthy support for scripting -- but sounds like you'd have to create them all from scratch.
Boston uses a workflow of building partially in InDesign then converting to LayoutChamp format to complete the page. It's pretty limited (but the integration was very limited when they started working with it). _________________ REMEMBER THE ALAMO ...
Hey, Dan Zedek from the Globe here. Chin's out on maternity leave for another week so I'll jump in. What we're using is a CCI plug-in called PageDesign that allows you to design in InDesign then convert everything into LayoutChamp. We're using it for all of our Business fronts and a few feature sections. It's quite buggy, though we've tested the next version and that works much better. Bottom line, though: what you end up with is a LayoutChamp page not an InDesign page. That's a big improvement over our current workflow of saving InDesign pages as uneditable EPS files and placing them in LayoutChamp but it's NOT the same as DTI where InDesign is the layout tool throughout production. The next version of Newsgate and NewsDesk both offer InDesign as a primary layout tool, but CCI's track record on delivering what they promise when they promise is… er… shaky. _________________ SND Boston
October 11-23, 2007
http://www.sndboston.com
So hypothetically, (no contracts signed), you'd say it would not be wise to organize design and copy editing so that some design-heavy pages were produced solely on InDesign/CCI and Incopy, while the production-heavy sections were produced through Word/CCI/Layoutchamp?
Or a more clear question: Do you have copy editors using InCopy to coordinate better with InDesign?
The InCopy part of it hasn't been released yet (though Boston may be involved in testing it).
6.13 (due Oct. 2007) will introduce the first phase InCopy functionality. 6.14 (due Spring 2008 ... maybe) builds on it, adding additional jump-page functionality.
The way it looks like it's going: You could, theoretically, have certain pages worked totally in InDesign/InCopy without going through the convert-to-LayoutChamp process. The stories and elements are all legitimate parts of the database, so they can be edited and processed all the way through. I wouldn't get frisky with it on much beyond features pages, special sections or advance centerpieces.
Also: Reporters could probably still be best left to work in Word. The InCopy part is really key for production, when you need to see accurate H&J of the story as it is on the page. _________________ REMEMBER THE ALAMO ...