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:Re: Usability: Tutorial *chapter* or *manual* From:Dan Roberts <Dan_Roberts -at- IBI -dot- COM> Date:Tue, 8 Apr 1997 10:09:04 EDT
I'd vote for a separate tutorial. 150 pages is quite enough for a
reader to keep in his head, esp when broken into several chapters. 150
pages of *one* chapter is too much for *me* to keep in my head. And,
IMHO, a manual of 350 pages is more than enough for a user guide, in
its own right.
______________________________ Reply Separator _________________________________
Subject: Usability: Tutorial *chapter* or *manual*
Author: Sue Heim <sue -at- ris -dot- risinc -dot- com> at tcpgate
Date: 4/8/97 10:00 AM
So, forget about the cost difference. If you had your choice, would
you prefer to have a 500 page manual that includes ONE WHOLE CHAPTER
on learning the program that is 150 pages long? Or would you prefer
to have a separate "Learning" booklet (likely saddle-stitched, btw)
and a separate user's guide?