{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Engineering Enablement by DX","title":"Implementing a developer portal | Karl Haworth (American Airlines)","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/aad47b34\"></iframe>","width":"100%","height":180,"duration":3249,"description":"Karl’s team at American Airlines were early adopters of Backstage, and in this episode he shares their journey of implementing and rolling out a developer portal. He also describes two of the extensions his team has built for their portal.\nDiscussion points:\n(1:24) Where the idea of building a developer portal came from\n(7:24) What the developer experience looked like before the portal \n(10:41) Initiating the project\n(14:16) The decision to choose Backstage \n(16:28) The V1 scope for the portal \n(19:14) Getting adoption for the portal\n(23:35) Defining success for the portal’s adoption \n(28:04) The ideal state for how developers will use the portal\n(30:56) Who should or shouldn’t invest in building a developer portal \n(33:14) Custom extensions Karl’s team has developed for their portal\n(37:46) What’s difficult about developing a new plugin for the backstage platform\n‍\nMentions and links:\nFollow Karl on LinkedIn\nThe Runway platform at American Airlines\nRead more on the engineering blog from American Airlines ","thumbnail_url":"https://img.transistorcdn.com/KGgcOtJYA_n91_n-WTCIj4wPicnSNHbF85xMwXKLznQ/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9iNjU2/NjdiYzQ1NmMxNTgx/Y2VhZDcyNWQ1M2Uy/YThlOC5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}