Title contains the questions. There are so many documentations of various styles out there.<p>Which are the best API documentations you know? Comprehensiveness, Readability, Usability/UX, Look&Feel, extensive use of standards... whatever factor makes it special/favourable.<p>Looking for role models.
Stripe, Parse, Twilio, SendBird.<p>This is a good overview of the different things that make up great docs: <a href="https://zapier.com/engineering/great-documentation-examples/" rel="nofollow">https://zapier.com/engineering/great-documentation-examples/</a><p>I think a great developer docs experience is a <i>really</i> tough thing to do well. You need to have great design, great writing, and great tech. The existing docs platforms out there (like Readme.io) all suck (especially for anything beyond REST API docs), so you really need to roll your own.<p>I've done some consulting in this area for clients who wanted amazing docs experiences, so ping me if you want some more ideas / feedback.
Airtable has a pretty awesome api documentation.<p>Basically, when you create a table and see its api documentation, it is generated on the fly to show you the rest endpoints specific to that table only.<p>Pretty awesome actually, worth checking it out.<p>Stripe has good api docs too.