It's a long shot, but if it were me I'd put everything in a text MarkDown/Up language (train everyone on it), then have things laid out in a managed directory t

It's a long shot, but if it were me I'd put everything in a text MarkDown/Up language (train everyone on it), then have things laid out in a managed directory tree that is administered by way of a source repository tool (Git, &etc.) The markup isn't necessarily a requirement, but some sort of text-based standard for how these documents are laid out would be important, imho. For print-processing/missionpacks, I'd use latex. Its really the best possible way to solve the text formatting problem, especially if you use a markup. You could have your own markup dictionary/language too, which would fit right in with latex files. So the whole policy group uses plain old text with smart formatting (so they are actually doing the work in-line) and doc generation through a latex pipe. Yup. Its the 70's all over again, and actually I'm becoming more and more aware of how non-ridiculous this is, while at the same time somehow being ridiculous. I wonder if there is a word for that ..