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.
Either writing programmer's guides is as much a dying art as tech authoring is rumoured to be, or my query is too daft to answer - but I got no responses to my original plea for help, so I'm displaying my capacity for audacity by reposting.
I have not worked on programmer's guides but now have the opportunity to do so. The initial draft I have seen looks rather sparse and not the best structure. Please can anyone recommend a decent example of a programmer's guide that I can look at for comparison?
I particularly need to know what the range of contents might need to be, as well as structure. We have format templates to use/adapt.
If the example contains or is accompanied by a Reference Design, that would be even better.
Many thanks for your help (pretty please?),
Heidi
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW