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.
Right. Although, I would suggest to build one on the fly as you need
to make decisions. Your job is not to align the effort, it's to make
the effort to produce the docs. If you use a basic tool (how about
TiddlyWiki) to trap your stylistic decisions as it makes sense to do
so, you'll then have all the meat ready to go when you have breathing
room to pen a formal style guide.
On Thu, Mar 11, 2010 at 3:10 PM, Mike Starr <mike -at- writestarr -dot- com> wrote:
> I have to disagree with devoting time to immediately creating a company-specific style guide. As the *only* technical writer, Melissa *is* the style guide. What she needs to do is hit the ground running and show them immediate real productivity. It's not in the company's immediate best interests to create a style guide for a department of one.
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-