RE: Beta documentation quality

Subject: RE: Beta documentation quality
From: Erika Yanovich <ERIKA_y -at- rad -dot- com>
To: "'p -dot- vuncanon -at- att -dot- net'" <p -dot- vuncanon -at- att -dot- net>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 13 Apr 2010 09:12:53 +0300

IMHO there is no such thing as Beta quality. Beta is a deadline by which the manual should be ready for the Beta customers. If you know in advance what is the customer application (what features they will and will not use), you can put TBD instead of explanation of features they won't use. You can also put TBD for nice-to-have info, such as appendices. In practice, sometimes there is no time to edit the manuals before Beta, but this is really something we should all try to avoid.

Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial:

Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at:

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Please move off-topic discussions to the Chat list, at:

Beta documentation quality: From: p . vuncanon

Previous by Author: Re: Microsoft Manual of Style questions
Next by Author: Re: MadCap Flare v6
Previous by Thread: Re: Beta documentation quality
Next by Thread: CrashPlan; was: Secure data storage, online and off;

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

Sponsored Ads