James Yu has written a blog post titled "Designing Great API Docs" on a company blog and it was interesting to see what kind of advice it had. The post suggests that multiple guides should come with the API documentation because when it stands on its own, it is much harder for someone to learn how to properly use it. If all you see are methods and classes, it can be difficult to figure out the flow of the code.