Articles

Different stakeholders interact with a developer portal throughout an API’s lifecycle. In this post we list 8 stakeholders and explain what they need to do their jobs.

Where does technical documentation stand with agile development methods? Watch and read about the talk Rob Woodgate (@agiledoc) did at the Write the Docs London-GDS mini conference on the practice of agile documentation.

Developer portals are important for your API's adoption and support. They are also a trust signal: a well designed and actively maintained developer portal shows that an organization is investing in its APIs. It helps convince developers that they can rely on them. In this post I’ll zoom in on the trust signals business model, partner policy, API quality, API uptime status, versioning policy, documentation and developer portal production quality.

At the API days in London, I gave a presentation about developer portals. In it I shared mental models and frameworks that I think can help improve the quality of a developer portal: I decided to write 6 dedicated blog posts about what I discussed.

Without proper documentation, an API team will spend countless hours on workshops, trainings and support. In this talk, presented at Apigee’s API Tech Forum in Amsterdam, Kristof Van Tomme explored 7 frameworks to help you build better API Developer Portals.

We wanted to understand the nature of trust issues and to figure out how we can overcome them in order to create a “frictionless” onboarding experience. Here is what we’ve found so far. We hope it’ll be valuable to both users and owners of developer portals.