REST API documentation
summary
Covers how to produce and maintain REST API documentation that stays current by keeping docs close to code. Discusses the problem of stale documentation when teams separate backend and frontend or expose APIs to third parties, and argues against storing docs in Google Docs/Markdown/reStructuredText alone, advocating embedding documentation with the codebase.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:33What is an API
- 2:39REST requirements
- 5:53REST API methods
- 8:03API documentation problems
- 9:45Documentation tools
- 11:56OpenAPI and Swagger
- 13:25Top-down vs bottom-up
- 17:00Swagger tool
- 28:01Code generation from spec
- 33:04Swagger features and alternatives
- 34:49Summary and recommendations
- 35:52Call to document APIs
- 36:14Q&A
related talks
35mDocumenting APIs: new era, same craft
26mDocumenting Your API Effectively: a Complete Tour of Spring-doc
50mSpring REST Docs: Documentation From Tests, Not the Other Way Around
26mA sensible API Document Management guide
25mThe link between technical documentation and developer engagement
38mThe Secret to Brewing up a Good API
57mDocumenting RESTful APIs with Spring REST Docs
30mSo You Need to Document an API?
