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.
I work in a documentation department of seven
writers. We use the Microsoft Style Guide and the
Chicago Manual of Style. I wanted to make two
First, these are not too difficult for a novice.
They are reference books, and you can take a much or
as little from them as you want. Both are easy to
use. Any manual you can get in an online or help
file format is doubly helpful, because you can
search for the terms you're interested in. The MS
guide is great for tips on documenting a GUI.
Second, no matter which other guides you use, create
your own style guide. Use this to record the style
decisions you make that aren't covered by the other
guides (spellings, casing, special definitions,
Our department style guide also spells out which
guides we use and their hierarchy. That is, we
specify which guide wins in case of conflicts. This
helps resolve tons of problems with over-zealous