I do like the PostgreSQL docs, they have a human feel to them and I usually get the answer I want pretty quickly.<p><a href="https://www.postgresql.org/docs/10/static/index.html" rel="nofollow">https://www.postgresql.org/docs/10/static/index.html</a>
Stripe is probably the best but I think Twilio is a close second. For both the page designs are easy to read, there are clear examples (some are even interactive), and the sites are easy to navigate.
Auth0's is pretty damn good. Clear docs, inline sample code...Auth0 even inlines your credentials into the example code if you're logged in.<p>[1] Auth0 - <a href="https://auth0.com/docs/api/authentication" rel="nofollow">https://auth0.com/docs/api/authentication</a>
I really like the Lua reference manual. All on a single page (e.g. <a href="https://www.lua.org/manual/5.3/manual.html" rel="nofollow">https://www.lua.org/manual/5.3/manual.html</a>), covers the complete syntax/semantic of the language, a few concepts as well as its Lua and C embedding APIs. All without bells and whistles. It surely helps that it's a relatively easy language. While I learned Lua, I basically never had to look anywhere else for information. I guess that's what a good documentation is supposed to aim for.
Surprised I don't see Django here. I'm always relieved to come back to a django codebase, that is the best documentation on any project or framework I've used.
Not an API, but the documentation for Haskell libraries is unbelievably good. Here's an example[1]. This documentation is generated automatically from source code, optionally decorated with comments using a simple syntax called Haddock[2]. Any package, whether it's built into the Haskell Platform or contributed by a user, has the same kind of documentation. Even if the author includes no Haddock comments, the documentation will include the type signatures, the hyperlinking, the instance lists, and other goodies like the minimal set of functions needed to define an instance of a class.<p>[1] <a href="http://hackage.haskell.org/package/base-4.11.1.0/docs/Data-List.html" rel="nofollow">http://hackage.haskell.org/package/base-4.11.1.0/docs/Data-L...</a>
[2] <a href="https://www.haskell.org/haddock/" rel="nofollow">https://www.haskell.org/haddock/</a>
Airtable's API. Every API document is specific to you, playing around with GET/POST/PUT/PATCH/DELETE requests is really straightforward to understand, even for someone that isn't familiar with how these requests normally work.<p>The sample json responses are also based on your data too, and the docs showcase what those look like
Side note, how do I volunteer or work part time writing technical documentation?<p>I feel like my writing skills and my ability to make code understandable and explicit to other readers would be a perfecy use for producing great documentation.
The requests package for python is nicely documented: <a href="http://docs.python-requests.org/en/master/" rel="nofollow">http://docs.python-requests.org/en/master/</a>
Not API, but Spark Java (<a href="http://sparkjava.com/documentation#getting-started" rel="nofollow">http://sparkjava.com/documentation#getting-started</a>) has one of the best Java framework documentation I've ever seen. Fairly concise + it has almost everything you need to build proper Web application using Java
Common Lisp HyperSpec - <a href="http://www.lispworks.com/documentation/HyperSpec/Front/index.htm" rel="nofollow">http://www.lispworks.com/documentation/HyperSpec/Front/index...</a><p>My choice is, perhaps, more indicative of taste/proclivity than anything else.
EVRYTHNG Platform docs are extremely thorough and versatile. There're also lots of guides and examples covering how to work with their platform. Taking into account complexity and amount of abstractions, those are one of the best docs i've ever read.
I really like the Requests quickstart docs: <a href="http://docs.python-requests.org/en/master/user/quickstart/" rel="nofollow">http://docs.python-requests.org/en/master/user/quickstart/</a>
I found sonic pi documentation engaging, easy to understand and comprehensive, <a href="https://sonic-pi.net/tutorial.html" rel="nofollow">https://sonic-pi.net/tutorial.html</a>