At the API days in London, I gave a presentation about developer portals. In it I shared 7 mental models and frameworks that I think can help improve the quality of a developer portal. 20 minutes is not nearly enough time to properly address all of the concepts. That is why I decided to write 6 dedicated blog posts about the models and frameworks I discussed and later create a separate series of blog posts that do a deep dive into implementation tools.
In the coming weeks we will be publishing these blog posts as part of our ongoing writing about developer portals, sequels to the blogpost series Kathleen wrote about developer portal components. These are the posts we’ve got planned:
- Part 1: Developer Portals - 7 Trust Signals that Help Your API Succeed
- Part 2: The 8 Stakeholders of Developer Portals (Feb 23)
- Part 3: 3 Maturity Models for APIs (Mar 2)
- Part 4: Inspire, Educate, & Authorise - Developer Portals and Jobs to be Done (Mar 9)
- Part 5: The Developer’s Journey - Developer Portals Need More Than an API Reference (Mar 16)
- Part 6: Public, Catalogue, Partner, & Utility APIs - 4 Developer Portal Archetypes (Mar 23)