Re: Difference between developer guide content and reference information

Subject: Re: Difference between developer guide content and reference information
From: Jeffrey Osier-Mixon <jefro -at- jefro -dot- net>
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Mon, 25 Apr 2005 00:52:01 -0700


What Bill said fits my interpretation as well.

Conceptually it sometimes helps to find out what questions the document is supposed to answer. A reference guide, API guide, or other specific reference document answers "what". A developer guide, programmer's guide, etc. answers "how".
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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

---
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.



Follow-Ups:

References:
Re: Difference between developer guide content and reference information: From: Bill Swallow

Previous by Author: Re: What Can We Do?
Next by Author: Re: Portfolios
Previous by Thread: Re: Difference between developer guide content and reference information
Next by Thread: Re: Difference between developer guide content and reference information


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


Sponsored Ads