[Author Prev][Author Next][Thread Prev][Thread Next]
[Author Index (this month)][Thread Index (this month)][Top of Archive]

Re: Starting an API Doc Project

Subject: Re: Starting an API Doc Project
From: Peter Neilson <neilson -at- alltel -dot- net>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Thu, 06 Nov 2003 08:19:09 -0500


Because API documentation is usually a second-priority project, you may
find that your engineering support has suddenly been reassigned elsewhere.
Plan for this calamity beforehand. You should at least have access to all
the source code and to the design documents, if any exist. Perhaps you'll
want a support team of several engineers, all of whom are aware of your
work and are helping review parts of it and are writing coding examples
for how to use the API.

Some events are hard to plan for, however. On my last API project, the
entire company vanished while I was still in the planning stages. I guess
I should have squirreled some of the stuff away for my portfolio, but as it
is, I've got absolutely nothing to show for three months of work.

On Wed, 05 Nov 2003 15:46:58 -0800, RAC <dshay -at- pacbell -dot- net> wrote:

Having read the numerous posts on this site about writing API doc, and
having worked on a few API projects myself, I'd like to know what you
think are the top 5-10 steps for getting started on an API documentation
project. Any additional tips or caveats you can share are most appreciated.



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

ROBOHELP FOR FRAMEMAKER TRIAL NOW AVAILABLE!

RoboHelp for FrameMaker is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to online Help, intranet, and Web. The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! Call 800-718-4407 for competitive pricing or download a trial at: http://www.ehelp.com/techwr-l4

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


Follow-Ups:

References:
Starting an API Doc Project: From: RAC

Previous by Author: Re: IMPROVING WRITERS' EFFICIENCY
Next by Author: Re: Seeking something like "The Elements of Technical Illustration"
Previous by Thread: Starting an API Doc Project
Next by Thread: Re: Starting an API Doc Project

[Top of Archive] | [Author Index (this month)] | [Thread Index (this month)]

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

Sponsored Ads