Style guides are essential aids for writers and editors who produce publications and online help projects—but does a style guide cover everything you need? Probably not.

Many writers and editors swear by a style guide, like the Chicago Manual, or the AP Style guide, when organizing, editing and writing publications. The Microsoft style manual is very helpful in technical writing and editing. Many corporations adapt elements of these to produce their own, distinctive style guides.

One of the most useful documents I've found when comparing help authoring tools is one by Matthew Ellison of Ellison Consulting, Ltd.: Comparison of HAT Paradigms and Workflows at http://www.writersua.com/ohc/suppmatl/suppmatl07/ellison_tools.pdf

Why was it helpful?
It examines:

What have I learned or gained most from TECHWR-L (and other tech writer email lists)?

1) connection and communication with a community of skilled, caring people

2) continual learning about the field of technical communication and its tools from those who use them and do the job

During my research on HATS, I found these great resources:

List of available HATs for help authors who use MS Word at:
http://www.mshelpwiki.com/wiki/tiki-index.php?page=AvailableTools

List of reviews on many of these HATS:
http://www.mshelpwiki.com/wiki/tiki-index.php?page=SoftwareReviews

I’ve also gotten good insight by emailing authors of software reviews. Many have responded within days and have been helpful.

Mostly however, I’ve found that trying the application is the best way to determine if it’s right for my projects and purposes.