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.
Subject:Types of documentation? From:Mr Smith <techwritermw -at- altavista -dot- com> To:TECHWR-L -at- LISTS -dot- RAYCOMM -dot- COM Date:27 Jan 2000 11:15:35 -0800
Thanks to everyone for being so helpful on my previous post. I have another general question about types of documentation, and then I'll probably fade back into LurkerLand for several months. :-)
How do writers typically differentiate training documentation from user documentation? My thoughts are that training documentation is designed around the training process (more examples and more handholding?), whereas user documentation should be used to use the hardware/software etc (in my mind, with a task-oriented approach).
My statements here are oversimpification...can anyone confirm/deny my beliefs? I'm sending this email because I'm trying to explain the difference to my boss, but I'm having a hard time being succinct.