Re: Document Identity
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:
What does your experience suggest to you?
Visit TechWhirl's Other Sites