The content devportal: Who writes the Docs?
summary
Research from DevPortal Awards, API The Docs showcases and Pronovix consulting finds that delivering an API product is heavily weighted toward docs — roughly 90% writing and maintaining — so teams set up explicit ownership (API product managers, a central hub team or decentralized product teams), editorial workflows, and feedback loops. The group builds a developer-journey model and a three maturity dimensions framework (developer experience, business maturity, operational maturity) to decide tooling, review cycles, and who owns each content type.
AI-written summary · about
chapters (4)
- 0:00Start
- 6:11What Can a Developer Portal Be and Who Are the Stakeholders
- 8:02The Minimum Viable Documentation for a Portal
- 18:35Starting Points
related talks
26mA sensible API Document Management guide
25mDo you know who's reading your Docs?
35mFrom Code to Clarity: Collaboration with Devels when Writing Product Documentation
26mBuilding successful API developer programs
20mOh My Docs!
27mWhy your API portal is so bad and what you can do about it
27mDev rel behind the firewall
26mThe three things your developer portal can't live without