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.
In article <199409250453 -dot- AAA16341 -at- one -dot- basd -dot- k12 -dot- pa -dot- us>,
<michael -dot- salsbury -at- cyberlink -dot- beaver -dot- pa -dot- us> wrote:
>Are style guides being used by most of your organizations? What
>sort of information is covered in your style guide? What parts
>of the style guide do you believe have been the most effective at
>improving the overall quality of your documentation?
This is my first tech writing job, I am my company's first official tech
writer, and (of course) there is no style guide. Furthermore, it's a
contract, and I don't expect to be around when the product is finished.
I'm concentrating less on writing a generic style guide than on
documenting the style and formatting that I'm using. This means
everything from word usage to style definitions, page layout, and
chapter organization. Functionally, I'm treating this as a programming
project that will need long-term maintenance.
--
--- Aahz (@netcom.com)
Hugs and backrubs -- I break Rule 6
Androgynous kinky vanilla queer het
The best way to get information on Usenet is not to ask a question,
but to post the wrong information.
