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.
> Hello Tech Writers,
> I have a doc that's experience an identity crisis. I am documenting a product that is a UNIX command-line application. Install and configuration are performed by UNIX commands/utilities. Read: there's no GUI anywhere and, once installed and configured, the product is automated save for troubleshooting, which is on-going. A disagreement broke out here regarding what kind of doc I am creating. Or, if you will, what to title the doc. The document includes the following chapters:
> The types/titles currently under debate are thus:
> Installation Guide
> Operations Guide
> User Guide
> What does your experience suggest to you?