We have a similar four-part documentation strategy: Tutorial, Technical introduction pages, Auto-generated API, and Samples Many people hate auto-generated API

We have a similar four-part documentation strategy: Tutorial, Technical introduction pages, Auto-generated API, and Samples Many people hate auto-generated API documentation because library authors do not write enough of it. For example here are my project's auto-generated documentation from source code, for two classes: https://gojs.net/latest/api/symbols/Diagram.html https://gojs.net/latest/api/symbols/Diagram.html https://gojs.net/latest/api/symbols/GraphObject.html https://gojs.net/latest/api/symbols/GraphObject.html That's 1238 words and 1408 words before you even get to the constructor. There should be a lot of information that comes out of the auto-generated API: What it is, what to know, different kinds of classes interact, and where to go next. Then of course a primary tutorial: https://gojs.net/latest/learn/index.html https://gojs.net/latest/learn/index.html And then conceptual Intro pages: https://gojs.net/latest/intro/index.html https://gojs.net/latest/intro/index.html (62 of them, covering everything from high level concepts to printing) Then, since so many people learn by example, hundreds of samples, organized with pictures and tags for each, with an explanation and commented code: https://gojs.net/latest/samples/index.html https://gojs.net/latest/samples/index.html