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.
chasity mcwilliams <chas -at- fcs -dot- uga -dot- edu> wrote:
>Is there a particular format that works best for a
>departmental guide?
>How do I determine what should be standard vs. personal
>preference?
If you actually want the style guide to be used, then keep it as
brief as possible and deal mainly with usages common to the
company and the industry. Otherwise, you can spend months
crafting a complete style guide, but you'll find that nobody will
use it, either for writing or for reviewing.
A useful style guide also needs to be thoroughly indexed. If
people can't find what they need to know, they won't bother using
the guide.
--
Bruce Byfield, Outlaw Communications
Contributing Editor, Maximum Linux
bbyfield -at- axionet -dot- com | Tel: 604.421.7189
"I dig a ditch, I shape a stone,
Another battlement for his throne,
Another day on earth has flown,
We're all working for the Pharaoh."
-Richard Thompson, "Pharaoh"
