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.
Style guides - doc standards vs processes (WAS: bad leadership an d tech writing)
Subject:Style guides - doc standards vs processes (WAS: bad leadership an d tech writing) From:"Metzger, Lucinda" <cmetzger -at- dukane -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 5 Nov 2001 09:08:07 -0600
Johanne Cadorette said,
"I'd like to emphasize the importance of documenting your own
documentation process. If you don't already have one, producing a style
guide is imperative. The style guide will ensure that the documentation
has the same look and feel across the board, and that all the
information is presented in a consistant manner. 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."
I'm curious -- how many of you include a "documentation roadmap" as part of
your style guides? How many of you have written up any type of roadmap at
all? In my department, we created two guides.
The style manual covers things like:
-Document layout
-Agreed-upon terminology
-Capitalization standards
-Product acronyms
-Trademark information
The procedures manual covers the actual processes, like:
-How doc projects are initiated
-How to pull a product sample from stock
-How to peer edit another writer's doc
-What form to use when sending a doc to review
-How to submit a drawing change to our drafting group
-How to post a doc to our website
-How to archive the files at the end of the project
Between the two guides, someone could resurrect the tech writing department
if (God forbid) we all get struck by trucks on the way to work.
On that cheerful thought, I'm getting back to work....
Cindy
cmetzger -at- dukane -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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
---
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.