~/talk

REST API documentation

TalkinRussianat РИТ++ 2017 · 2017-06-05..06-06· [api-design, documentation]
links:none on file
slides:none on file

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

  1. 0:00Introduction
  2. 1:33What is an API
  3. 2:39REST requirements
  4. 5:53REST API methods
  5. 8:03API documentation problems
  6. 9:45Documentation tools
  7. 11:56OpenAPI and Swagger
  8. 13:25Top-down vs bottom-up
  9. 17:00Swagger tool
  10. 28:01Code generation from spec
  11. 33:04Swagger features and alternatives
  12. 34:49Summary and recommendations
  13. 35:52Call to document APIs
  14. 36:14Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.