When Book File Collaboration Won’t Work
The Book File Collaboration Workflow has one hard rule–in order for automatic page numbering and unified output to work, each component document must comprise strictly contiguous pages with no blank or extraneous pages. For magazines, newspapers, newsletters, magalogs, and other documents where stories jump, pausing on a particular page, skipping other content pages, and then picking up again farther into the publication, the one rule of book file collaboration could be a problem. (If your publication doesn’t jump stories, it’s not a problem.) InDesign can’t thread a single, continuous story across multiple documents; threaded frames may only be in the same document. Therefore, if a feature article jumps from page 19 to page 32, you’re left with a dilemma. You have a choice between four possible solutions for that dilemma:
- Make pages 19–32 one document, inclusive off all content pages between, thus making it impossible for more than one designer to work at any given time on any page between 19 and 32.
- Make pages 19–32 one document, but leave blank any pages not directly part of the single feature story. Any intervening pages and sections are still their own separate documents, enabling other designers to work independently and concurrently on their respective pieces. This method isn’t new–it’s what magazines and other periodicals typically employ. There are two downsides to this method: automatic page numbering goes haywire because of the extraneous pages, and it forces extra pagination work and a greater potential for mistakes immediately before going to press.
Many component documents using this method include numerous pages that serve no function other than as placeholders for content on which someone else is working. When the pages are locked down, just before the issue is put to bed, someone has to sit down and either combine all the components into a single document via drag and drop or go through each document, printing or exporting content pages manually while ignoring placeholder pages. When pages are exported to PDF, EPS, or another format, the numerous resulting files are then either combined into a single document (for instance, one large PDF), imposed in-house into a single document, or named after their page numbers and sent out for imposition (whereupon someone hopes very, very hard that the imposer doesn’t make a mistake).
- Continue with the Book File Collaboration Workflow, making page 19 one file, page 32 another, and dividing the intervening pages as needed and independently of the jumped story. In that case, the story is manually broken on page 19, with its last line tweaked and a jumpline inserted, and then the overflow copy is added manually and independently to page 32, again, with a manually inserted and maintained Continued From jumpline. Last-minute edits to the story or to the layout that affect story composition require editing two documents instead of one.
- Augment or replace the Book File Collaboration Workflow with a different methodology. See if your workflow can employ the InCopy LiveEdit Workflow (Adobe’s term, not mine) or the Placed Page Collaboration Workflow (I am pretty sure I’m the first to coin this one, so please send me a nickel every time you use it) or both. I’ll discuss both of these methodologies below–the latter in the very next section, “One Page, Many Designers,†and the former a few pages hence in the section “Collaborating with Editorial.â€
Just to be clear: If your publication doesn’t jump stories outside the pages assigned to each creative, you can use the Book File Collaboration Workflow without the aforementioned problem. Do still read the rest of this chapter, though, as none of these methodologies is necessarily exclusive of the others.
One Page, Many Designers
Yesterday there was a one-to-one, one-designer-to-one-page, relationship so inflexible it may as well have been cast in iron. Today, the paradigm has shifted. Now, with InDesign CS3, a many-to-one relationship is possible. Many designers may work simultaneously on one page–or, more accurately, on portions of the same page. In Figure 12.2 you’ll see a flowchart diagramming an example of what I’ve dubbed the Placed Page Collaboration Workflow.
Figure 12.2 Diagram of a Placed Page Collaboration Workflow in use on a single page
In the diagram, a single-page magalog layout is divided into three separate areas. Three separate designers will work concurrently, one on each area, all never leaving InDesign. Rachael (the redhead), is responsible for copyfitting and setting the six product listings in the middle of the page, while Carlos (in the middle) takes care of designing the sidebar and feature box. Kim (at the bottom with the ponytail) is the lead designer on the page, so she’s designing the background imagery and setting the headline, deck, page introductory paragraph, and static elements like the folio. Previously, trying to split the work on one page among three designers meant each would have to take a turn, each one waiting to begin work until the last has finished. All three designers under this scenario are working concurrently, on the same page, in InDesign.
The principle is simple, one with which you’re already intimately familiar. Let’s look at the basics of your current workflow.
If you work on advertising-supported publications, for instance, you almost certainly accept PDF or EPS press-ready ads from agencies, right? Someone far away designs an ad, FTPs it to you, and you drop it as is into the appropriate slot in your layout. If you don’t accept outside creative into your layouts, you do create elements and sections of at least some pages in Photoshop or Illustrator. That artwork (or agency art) is placed into InDesign as a linked asset. Should the asset need to be altered, it’s edited in its native application and the link merely updated in InDesign. Thus, while you’re working on the composed page in InDesign, someone else could be working at the same moment and independently in Illustrator on the pie chart for page 6. Neither of you will hinder the other’s work because, as a linked asset, that AI or PDF pie chart is a wholly separate document from your INDD layout. You do this day in and day out with placed assets, so you know how it works.
Now, substitute another INDD file for the AI or PDF. Instead of a pie chart, page 6 contains a table or other elements better done in InDesign than outside it. InDesign CS3 now accepts other InDesign files as placed and linked assets. That’s what Rachael, Carlos, and Kim are doing. Each is working in InDesign on a separate INDD or INX document. The final, composited page in the Figure 12.2 flowchart is a fourth document (or not; maybe Carlos is working in the master while Rachael’s and Kim’s pieces will be placed into his document). For the sake of argument, let’s assume a fourth document collects the three designers’ separate documents. The compositor uses File > Place or drag and drop from Bridge, Finder, or Explorer to import the designers’ three separate INDD files exactly as he would a trio of TIFFs, PSDs, PDFs, or whatever. The placed assets are then arranged to form the composite page–just like pages you lay out every day with images and artwork created outside InDesign. That’s the Placed Page Collaboration Workflow.
Another cool aspect of compositing a page by placing INDD files is that the compositor’s tasks of manual asset positioning and transforming can be completely eliminated. Glance again at Figure 12.2, paying particular attention to the component pieces. Notice that they’re all the same size and, except for Kim’s background, contain copious white space. Each piece is the exact size of the final page. If your composited INDD document is 8.5×11 inches, make each page asset 8.5×11 inches. The bounding box of each placed page will then also be 8.5×11 inches. Not only does that enable each designer to work with a sense of how his work fits into the page as a whole, it also means the asset can be placed with minimal positioning work. Rachael’s, Carlos’s, and Kim’s art can all be placed at the same time, aligned to each other’s top and left edges with two quick clicks of buttons on the Control panel or Align panel, and then easily positioned to the 0,0 origin. No one has to zoom in and precisely position the pieces to one another because they are all the same size, ready to align perfectly with one another. Cropping is unnecessary, too, because empty space on the InDesign document page is transparent; each asset will show through the negative space in the one above it. They’ll even blend with each other if transparency or blending modes are used. In my flowchart, the black background of Carlos’s sidebar is set to a Multiply blending mode at 85%. When it overlays the fingerprint image in Kim’s section of the page, the sidebar will enable the white fingerprint ridges to show through as 85% black ridges. The red feature box also blends with the other part of the fingerprint via another blending mode.
How do I know what everyone else is doing? You can’t lay out a page in a vacuum. Again, InDesign CS3 can place other InDesign files as assets. So, to keep abreast of what everyone else is doing in his portion of the page, place each page component document on the pasteboard. Assuming everyone is working from files stored on a network server accessible by all, Rachael can place on her pasteboard Carlos’s and Kim’s INDD documents, Carlos can place Rachael’s and Kim’s, and so on. When any one of them saves the document, InDesign will notify the others that the linked asset has been changed and ask if the link should be updated. If you’ve got a good group of people fastidious enough to clean up after themselves, they can even place the other designers’ documents on the page instead of the pasteboard. The effect then is that three people are all working simultaneously on the composite layout. (Fair warning: It can be a little creepy at first to watch parts of your page change as if by supernatural means.)
Next: Solving the Problem with Book File Collaboration
This, in my opinion is ridiculous!
Design by committee to the unth degree. Having been in publishing for almost 20 years, I have yet to experience a scenario where the most time and cost efficient way of doing things is to have several designers working on the same FILE at the same time.
What Adobe seems to leave out of their vision of ‘workflow’ is the customer – you know, the people that pay people like us so they can change their minds at the drop of a hat.
Sure, one application may work, but five personalities working harmoniously at the same time – that’s a joke.
Simultaneous concept development… never works.
My mind’s eye envisions a server bulging with dupes of pages and folders from people who are, for a lack of a better word… in a state of flux.
Sorry, this seems like a poor man’s version of Composition Zones. Last time I checked in Quark 7 you simply selected an area, a page, a spread or a section of a document you wanted to “farm out” and with a little bit of practice, anyone on the network or Internet (if invited) automatically gets a document with only their bits editible. Upon saving, your grayed out areas then update. It’s a lot different when software is designed specifically for colaboration as Quark 7 and 8 are, as opposed to the Rube Goldberg approach which has been available for years already. BTW: Our customers who use this are growing and would never go back to not using it. It’s like taking processors out of your Xeon chip…parallel processing is where it’s at.
I like the little comment boxes, they are nice. :)
No matter how you look at it, cool collaboration tools in Quark are useless if you are still stuck with a lame layout application.