You’ve already told them what’s possible, so here you need to show them. This meets a developer at a basic level of knowledge and holds their hand to a quick win. The most important API documentation you can provide is a quickstart or getting started guide. Between these two pages, developers can figure out in a hurry (and without even signing up) whether they’ll be able to solve their problem with Plaid. On the developer homepage, you can quickly see more about what’s possible: transactions, income, balance, and more is available with Plaid. Since the API is core to everything the company does, you can also find docs in the global navigation. Keep in mind that this is the homepage for the whole company. In one sentence, developers know they can use Plaid to connect to their users’ bank accounts. Plaid could have easily written something hand-wavy on its homepage like “the future of financial services.” In fact, that line shows up further down the page, but in the context of five common use cases. Then, ensure you clearly communicate the main benefits of your API or platform. Make it easy to find your portal or developer homepage. ![]() Show Developers What’s PossibleĪ developer wants to quickly answer whether your solution will solve their problem. Based on great examples of each, you can implement some of these ideas today. This post will cover these common areas of documentation, plus some areas you might not typically see called docs. While nobody makes bad documentation on purpose, everybody can help make it better. LogRocket shares lessons on its developer blog.Dropbox lets developers interact with its API.APIMatic provides language-specific content.To make the easier, we’ve focused on one primary lesson for each: Review these 9 great examples of API documentation and emulate them with your own docs. Good API documentation makes it easy for developers to use, reference, and explore. The best API documentation reaches beyond simple accuracy. However, one place many developers agree is the most annoying part of using a new API or dev tool: dealing with its documentation, which is often outdated and inaccurate. Ask 10 developers a question and you’ll usually get 10 different answers.
0 Comments
Leave a Reply. |