But even if you're committed to writing great API documentation, it's hard to know where to start.There's no API documentation guru whose mentorship you can seek, nor a standard how-to guide for documenting your API.Because the documentation is often the first thing a developer encounters when working with your API, it's the only way for them to get an impression of your product.If your team can't update your docs after a new feature has been launched, what else are you overlooking?And once they became known for their thorough and remarkably clear documentation, they had a reputation to uphold.
Humans come from all backgrounds, with different experiences and perspectives that all need to be addressed.
But that doesn't mean you should spend months on your documentation before giving your consumers access to it. They're robust, thorough, and come with plenty of resources and tutorials that let you dive right in.
They didn't build it overnight, but they did have all the proper pieces in place: As they built out their product, found more use cases, and addressed queries, they updated the site, equipped with a nicer, sleeker UI.
They make assumptions about API consumers' knowledge base and how much they're willing to put up with to get a good understanding of how the API works.
But your API consumers aren't so different from a standard software user, even if they are developers.