RE: User Guide - best practices

["Maggie Secara" <maggiros -at- adelphia -dot- net>]

How about printing the shorter guide, and putting the bigf on in on-line
help?  That way deverythign's available but you don't have to scare anyone
with a big book.

Justa thought,


Maggie Secara

> -----Original Message-----
> From: bounce-techwr-l-84814 -at- lists -dot- raycomm -dot- com
> [mailto:bounce-techwr-l-84814 -at- lists -dot- raycomm -dot- com]On Behalf Of Lisa Conway
> Sent: Friday, July 26, 2002 7:16 AM
> To: TECHWR-L
> Subject: User Guide - best practices
>
>
>
> Hi all,
>
> I'm a tech writer for a software company. My question concerns our user
> guide. It is almost 500 pages and includes both descriptions of
> every window
> and the various tasks a user would perform when using our application. We
> also have another shorter manual for the same application that
> only includes
> the tasks. My question is should we just go with the task based
> manual or is
> it necessary to have a user guide that includes detailed descriptions of
> every window? >


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  Your monthly sponsorship message here reaches more than
  5000 technical writers, providing 2,500,000+ monthly impressions.
  Contact Eric (ejray -at- raycomm -dot- com) for details and availability.

Buy RoboHelp Deluxe starting at only $798: you'll get RoboDemo, the hot new
software demonstration tool that's taking the Help authoring world by storm,
together with RoboHelp Office. Learn more at http://www.ehelp.com/techwr-l
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.