The three things your developer portal can't live without
summary
Developer portals need three concrete things: accuracy via the 30/90 review cadence (review at 30% for IA, 90% for details), a published SLA for doc fixes, style guides and changelogs; usefulness measured by bounce rate, on‑site time and search performance, with time‑sensitive front‑page content, forums staffed by the team, and sustainability through user‑generated content; and security including identity management/SSO, portal access models (internal/private/public), and API controls like validate parameters, SSL, auth and threat detection.
AI-written summary · about
chapters (9)
- 0:00Intro
- 2:40What is a developer portal
- 4:13Accuracy
- 7:51Usefulness
- 9:50Sustainability
- 16:44Security
- 19:27Trust
- 21:43Conclusion
- 22:00Questions
related talks
27mWhy your API portal is so bad and what you can do about it
17mDevelopers Documentation: your secret weapon
23mThe content devportal: Who writes the Docs?
30mBuilding Developer Documentation with a Fully Remote Team and Community
43mUseful and Beautiful Developer Docs and How to Create Them
35mLong-term Documentation Maintenance
25mTest developer experience, not code
39mDevelopers Documentation: your hidden strength