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.
"I would prefer something more along the lines of end-user
documentation and training, but I'm okay with software documentation.
Any thoughts and ideas would be greatly appreciated. "
David,
Like others that have replied, I am mystified by the end-user vs. software
distinction you make.
Documentation that accompanies a product (or is the product) is end-user
documentation. The end-user is the variable that defines how different the
docs have to be. API documentation is an end user doc for the application
developer; installation documentation is an end user doc for the installer;
"how to" instructions are end user docs for the dad building the swing-set,
etc.
I am uncertain of the origin of the term end-user doc, but my faulty memory
puts emphasis on the polishing of documents for delivery and a way of
distinguishing "internal" documents from public documents. In other word,
marketing speak that became mainstream. These distinguishing features still
hold true. End-user docs should be polished (but often aren't) and are
quite different from internal documents (but often aren't).
Regardless of distinctions and quality of documents, you can make a living
off of writing internal docs for software companies, insurance companies,
banks, etc. You can also make a living writing end-user docs for insurance,
banking, marketing, hardware, etc.
Software is just a large market for hiring writers.
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005
---
You are currently subscribed to TECHWR-L as archiver -at- techwr-l -dot- com -dot-