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 thought the OP was looking for more a programmer's guide, not an API doc.
There is a major difference between the two, even though the audience is
similar.
API/SDK doc (your specialty) is aimed at developers who have familiarity
with the ecosystem to understand the guts in more depth. It's a reference.
A PG is more for the developer who is getting started, may be branching
from a similar system, or deciding between tools. It's a how-to manual.
A PG would provide best practices for the problem the system solves (and
how the system is meant to be used) and not just a collection of features.
The SDK can add programming guide-like content, but the intent is more for
use as a cookbook than an explanation of the system.
-Tony
On Monday, August 31, 2015, Marsh, Ed <Ed -dot- Marsh -at- gs -dot- com> wrote:
> I don't disagree that Drupal's docs are all over the place (as well as its
> whole ecosystem, but that's another debate), but the API doc section at
> least shows some consistent structure, and I think that's what the OP was
> looking for.
>
> Ed.
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Learn more about Adobe Technical Communication Suite (2015 Release) | http://bit.ly/1FR7zNW