Re: Documentation structure

Subject: Re: Documentation structure
From: TechComm Dood <techcommdood -at- gmail -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Sun, 6 Feb 2005 10:53:25 -0500


In my experience, you don't pick what types of documents you'd like to
see in a product release and then validate them. Rather, you look at
the product, determine what the audience for the product will need in
order to use it, and write it up. Then you can slap labels on the
different deliverables as they become known.


On Sun, 6 Feb 2005 15:26:08 +0200, Caroline Tabach <Caroline -at- radcom -dot- com> wrote:
> The company would really like to give the users "impressive" documentation! Are there additional types of documents that you generally distribute with software products that have not been mentioned here?

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo:
http://www.webworks.com/techwr-l

Doc-To-Help 7.5 Professional: New version with new features, improved performance and reliability, plus much more! Download your free trial today at www.componentone.com/techwrlfeb.

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.



References:
Documentation structure: From: Caroline Tabach

Previous by Author: Re: Request for Guidance
Next by Author: Transitioning User Expectations from Feature to Task-Based Information
Previous by Thread: Documentation structure
Next by Thread: Re: Documentation structure


What this post helpful? Share it with friends and colleagues:


Sponsored Ads