RE: Style guides - doc standards vs processes?

["Cadorette Johanne" <johanne -dot- cadorette -at- locusdialog -dot- com>]

About my original post: <<A documentation roadmap would also be useful.
Map out the documentation process from a-z, matching each step in the
development process to one in the documentation process.>>

The "roadmap" was in fact (I dug it out)a simple, one-page flow chart
with two columns:R&D and Documentation. The first stage of R&D, which
could be something like "specs and use cases," might for example
correspond to the "research and outline" stage in the documentation
column. "Alpha release" in the R&D column could correspond to "draft
documentation," and so forth. Really, it was pretty basic, but it meant
we (the doc. team) knew what had to be done by when. If a date for a
beta release was announced, we knew that meant we had to have a finished
manual by that time. 

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Be a published author!  iUniverse gives you: a high-quality paperback, a
custom cover design, and distribution to 25,00 retailers.  Join our almost
10,000 published authors today. http://www.iuniverse.com/media/techwr

  Your monthly sponsorship message here reaches more than
  5000 technical writers, providing 2,500,000+ monthly impressions.
  Contact Eric (ejray -at- raycomm -dot- com) for details and availability.

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.