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.
Does anyone know of any resources on putting together the documentation
for an SDK? We did the first draft of our SDK recently, and while all
the programmers (including a contractor newcomer) think it's just fine,
the organization seems almost incoherent to me. I can't seem to get a
handle on specifics of the audience and what they need from the
documentation. Also, I'm having trouble drawing conclusions based on
existing SDK documentation. (There's a key out there somewhere that
will make everything fall into place--I just need to find it!)
Do many people have to write SDK documentation or is it a rare task?
++++++++++++++++++++++++++++++++++
Sella Rush mailto:sellar -at- apptechsys -dot- com
Applied Technical Systems, Inc. (ATS)
Bremerton, Washington USA
Developers of the CCM Database
