APIs are a conversation, not a broadcast. Blogs, changelogs, newsletters, and status updates keep consumers informed and invested in what I am building. Consistent communication is what turns a list of endpoints into a community.
Communication
Beta
Stop 15
Policies at this stop
API Outreach and Content
Require that an API is actively communicated through ongoing content and outreach, including blog posts, changelogs, and updates that tell the story of what it does and why it matters. An API launc...
Blog Feeds
A blog RSS or Atom feed provides a simple way to syndicate information and updates about APIs with producers and consumers, allowing it to be pushed out to where they are located and regularly cons...
Blogs
A blog helps provide a regular channel for publishing relevant stories and information for both producers and consumers of an API, providing a simple, informative, and recurring way to stay in enga...
Communication Status Page
Every API must maintain a public status page that reports current health, active incidents, and scheduled maintenance in real time. I require that consumers be able to check the state of an API the...
Community Engagement Channels
Require that an API provides real channels for its community to engage, whether a forum, chat, mailing list, or regular office hours. Consumers need a place to ask questions, share solutions, and c...
Developer Relations Program
Require that any API meant for real adoption is backed by a developer relations function responsible for supporting, advocating for, and growing its community of consumers. Endpoints and documentat...
Videos
Videos offer an engaging way to provide information and updates with producers nad consumers of APIs, demonstrating how an API can be used, providing webinars, workshops, and other useful videos ab...
