TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Collaborative Documentation Review Process From:Bill Swallow <techcommdood -at- gmail -dot- com> To:Missy Smith <techpubsmistress -at- live -dot- com> Date:Mon, 7 Dec 2009 12:03:43 -0500
We've always used Acrobat (pro is only needed for the review document
creator) and review comment features, either via email or served
document. Everyone involved (not just writers) has loved this
approach.
To speak to the one reviewer's reservations, you can use comments,
highlighting, strikethroughs, and other markup for reviewing
documents, and ALL of them allow you to add a comment associated with
the mark.
In a served review doc, reviewers will be able to see each other's
comments and respond to them, which can alleviate some of the monkey
in the middle back-and-forth that writers can find themselves in
resulting from trying to resolve two strong differences of opinion.
And of course, all comments are rolled up neatly for the writer, who
can then generate a report of all comments.
Even if the PDF is emailed out, the writer can collate comments back
into one file.
Just remember to enable review commenting before distributing the PDF!
Then all any reviewer needs is Reader to mark it up.
HTH,
Bill
On Mon, Dec 7, 2009 at 11:37 AM, Missy Smith <techpubsmistress -at- live -dot- com> wrote:
> What software and process do you use for collaborative documentation review?
>
> Currently we are looking into using SharePoint as a repository for documents set for review. We would publish a .pdf of the document and use Adobe Acrobat Pro for comments and markup.
>
> One of our reviewers commented that Acrobat "sticky notes" can be difficult to use when a reviewer wants to submit large amounts of data for inclusion in a document. Some formatting can be difficult to convey also. This reviewer also commented on how they liked Word commenting because you could get a fnal copy view that is much easier to read than Acrobat's comments list and markup symbols.
>
> I am charged with coming up with a new process. What do you do?
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Help & Manual 5: The all-in-one help authoring tool. True single- sourcing --
generate 8 different formats and as many different versions as you need
from just one project. Fast and intuitive. http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
