Beyond the Spec: Making OpenAPI More Human
summary
Argues that poor docs and complexity block adoption — Postman shows 55% lack of documentation, private APIs make up 56% of consumption, and some firms get >75% of revenue from APIs, so quality matters. Recommends manual edits to autogenerated OpenAPI output, baking in inclusivity and screen‑reader support, and using linting/CI with Spectral to enforce standards. Shows a shipped OnlyOffice API reference with a three-panel API reference, live playground and working copy‑code buttons.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:55What is ONLYOFFICE
- 3:40Challenges developers face with APIs
- 7:57Developer experience matters
- 9:21Roles in DX and relations
- 12:51Auto-generated docs problems
- 14:18Inclusive API examples
- 15:22Open-source tools for APIs
- 16:24Key strategies
- 18:11Improved API docs examples
- 20:15Closing & Q&A
related talks
35mOpenAPI for Documentarians
24mBuilding an Accessible API Spec with Traditional Engineering Teams
27mGetting developers hooked on your API
21mLet there be docs!
38mZen And The Art Of Automanually Creating API Documentation - An Inquiry Into Process
38mThe Secret to Brewing up a Good API
25mThe Life Changing Magic of Becoming API First
25mDo you know who's reading your Docs?