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.
> I am not very experienced in documenting API so I am a little uneasy in
> pushing back! Hence my question.
You just gave an excellent reasoning for your pushback. You don't need
to be an expert in documenting an API to recognize common sense via a
small bit of audience analysis (which you appear to have done).
> Are API commands typically combined across product lines, or from one
> generation to the other of the same product line?
Well, consider this. You have API1 installed and hit the reference.
You see a cool function and want to use it, so you try implementing it
but you can't, because it doesn't exist... it's for API2. Are the docs
wrong? Did you as a user do something wrong? Is the product crap?
If you play the role of user and find yourself asking these
hypothetical questions, guess what? Something's wrong and needs to be
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.