The Rocky Road to DocOps
summary
A documentation program replaces scattered Word files and ad hoc publishing with an automated pipeline that renders one canonical API specification into both internal and external portals using Redoc and Drupal integrations, cutting seven files down to one API spec and avoiding manual publish steps that once took eight hours with nine people. Tooling drives process, local linting and editor feedback prevent blocking CI gates, workshops train engineers, and 90% of the API workflow is now documented and producing measurable author pride.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:38ABN AMRO & me
- 6:19Requirements gathering
- 12:19Tooling investigation
- 16:24Process definition
- 18:32External API process with docs
- 19:31External API process v2
- 21:51Development
- 24:03Training and coaching
- 24:47Takeaways
- 26:49Creating resources
- 29:35The destination...
related talks
33mDevOps Friendly Doc Publishing for APIs & Microservices
19mStreamlining API Documentation: Proven DocOps Strategies
35mBuilding Docs like Code: Continuous Integration for Documentation
47mDocumentation Is Fine, Don't Worry
44mPushing documentation (so it doesn't hurt anymore)
35mOpenAPI for Documentarians
38mZen And The Art Of Automanually Creating API Documentation - An Inquiry Into Process
45mDocs as Code Fix a poor documentation culture in your organization