> Some notes/questions:
> Working with InDesign/Desktop Publishing:
> I'd imagine XML output would satisfy most needs, since most desktop
> publishing programs have XML import capabilities. Adobe has some good
> resources on InDesign+XML integration: http://www.adobe.com/products/indesign/scripting/
> (though for a true publishing solution, I'd imagine you might still
> need a go-between app, that facilitates communication to and from
> InDesign and Nando)
Last time I tried that, InDesign CS3's XML import was only good for
creating catalogs and similar documents. You couldn't drag a group of
story elements (headline, byline, content, photo, etc.) from a library
onto the page and then tell InDesign to place a particular XML
document into those elements. Has anyone figured out how to do that,
perhaps in CS4? The new version's docs make it look promising...
> Staffer role:
> On pg 5: "Staffers are normally placed into one of these departments
> as their primary responsibility, which is reflected in their dashboard
> and other views." Just wondering if staffers can be placed across
> departments? A definite use case in smaller publications.
Most of our writers don't have a "home" department and so it'd be
important not to force them to have one. Some editors, even, have
multiple departments, especially when we have vacancies and other
editors fill the gaps.
From the spec, it wasn't clear to me what would prevent the dashboard
from listing the staffer's articles from all sections. For editors, it
should be easy to add multiple widgets that list all the pending
articles in each section of responsibility.
> I was contemplating how to handle the managing editors
> and EIC roles, and I think the answer is simply to not place them in a
> department and therefore they get an unfiltered view of everything
> (alternatively, we could have a "special" department that sees
I wouldn't start adding special cases. Have a many-to-many
relationship between departments and sections, and then you can choose
which sections are a part of each department. For 99% of the cases,
you'd only add one section to each department, but you'd add them all
to the EIC.
A super-department that sees everything wouldn't work for us, since
the EIC controls editorial content and the Publisher controls other
stuff, like business and advertising. So we'd want the EIC to see all
of the content sections and the Publisher to see all the non-content
stuff that's still managed by the CMS.