The Four Stages of OpenAPI
summary
Explains a practical four-stage OpenAPI workflow: convert legacy Word docs into a compilable OpenAPI file, then maintain and enrich the reference forever, plus prototyping and API‑first where code is generated from the spec. Claims conversion routinely takes three to five times longer than writers expect, that debugging OpenAPI is awkward, and that Redocly plus VS Code and Postman are used to compile, run calls, and validate. Emphasizes writers adopt a developer mindset and only edit description tags while code is generated from the spec.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:23Great API documentation
- 8:19OpenAPI overview
- 13:19Stage one: Convert docs to OpenAPI
- 27:55Stage two: Maintain and enhance docs
- 30:01Stage three: Prototype APIs
- 31:07Stage four: API-first approach
- 32:59Q&A
related talks
35mDocumenting APIs: new era, same craft
21mDesigning APIs with OpenAPI: Build the Right APIs the Right Way.
19mSecure and accelerate APIs' lifecycle with the OpenAPI specification
30mAPI Code First vs Design First
19mAvoiding the 8 Wastes of Lean API Development with OpenAPI & APIOps.
46mOpenAPI & .NET: You're Doing It Wrong!
47mContract-Driven API Development with OpenAPI Specification
35mOpenAPI for Documentarians