Can Affordance Catalogs power up your Dev Portal?
summary
Claim: an Affordance Catalog that lists reusable actions (not services) powers discovery and cuts developer rework. Built on an API‑first hypermedia stack (JSON‑LD/RDF ideas mentioned) and used at Vesti to expose capabilities like a single display name update affordance across profiles and chat rooms. The catalog stores intent-level metadata so front ends discover actions rather than hardcode endpoints, and early usage shows it works in production, reducing duplicate endpoints and developer friction.
AI-written summary · about
chapters (12)
- 0:00Intro
- 2:10Welcome
- 3:25Why are we here
- 4:25Affordance Catalogs
- 8:20N1 Problems
- 11:20N2 Problems
- 14:15N4 Names
- 16:25Apis are Specious
- 17:15Names
- 20:05Design lineage
- 21:45Definitions
- 22:50Summary
related talks
26mAn Easier Path to a Rich Catalog
23mAgentic Backstage: How To Manage an AI Software Catalog
31mRethinking Data Catalogs: The Promise and Pitfalls
17mDeveloper Portals, API Catalogs, and Marketplaces
25mUnlocking API Potential: The Power of Developer Portals
33mThe Future of DevPortals
23mUnlocking the Catalog: Providing a Platform CLI for Backstage
23m3-Step Path for Fixing Data Discoverability