Developer portal
summary
Joiners often waste hours hunting docs across Confluence, Slack and drives; a developer portal claims to stop that by centralizing a Backstage service catalog with search, starter templates, API listings and links into source control and CI status so teams find owners and integrations quickly. Warning signs: dumping everything in, recreating tools inside the portal, no owner, and no tracking — instead plugin architecture for integrations, structured concise content, and measure adoption and KPIs to prove reduced discovery time and drive ongoing upkeep.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:30Developer doesn't know where to look, how to track down
- 2:28What is a Developer Portal?
- 2:42Discoverability
- 4:06Catalog of Developer Services
- 5:26(Typically) Catalog of Software Products
- 6:34Antipatterns
- 6:59Putting Low Quality Information and Products into the Portal
- 8:50No owner and maintainer of the Portal
- 10:12Not measuring the impact and adoption
- 12:01Recreating tools inside of the portal
- 12:20Backstage An open platform for building developer portals
related talks
32mDeveloper Portal? I just want to code
38mEmbracing Developer Portals in Software Development
28mThe Game-Changing Role of Developer Portals
37mTransforming DevEx with Internal Developer Portals
25mThe Developer Portal: Open the Gate to Productivity 🚀
25mUnlocking API Potential: The Power of Developer Portals
29mThe Future of API Integration
39mDoing more with internal developer portals