DevOps Friendly Doc Publishing for APIs & Microservices
summary
An internal doc pipeline called Pub Hub is built and used at Cisco to normalize Swagger/OpenAPI, RAML and Markdown into a consistent site, driven from GitHub and integrated into CI/CD with staging and previewers. It accepts multiple inputs, uses open-source processors, supports localization, and provides both continuous deploy and approval workflows. Teams report saved time, more engineer-authored docs, and easier internal-to-external publishing, while remaining work includes linting, aging metrics and measuring adoption across developers and writers.
AI-written summary · about
chapters (15)
- 0:00Intro
- 2:33API Developer Experience
- 3:06App Dynamics
- 4:37API Reference Docs
- 5:23How are people doing this
- 7:10Problems
- 8:23API Reference
- 9:42Initial Ideas
- 12:09Project Overview
- 13:18Project Setup
- 14:31Samples
- 15:08Feedback
- 22:58Recommended resources
- 23:41Cisco DevNet
- 27:55Automation
related talks
40mThe Rocky Road to DocOps
19mStreamlining API Documentation: Proven DocOps Strategies
35mBuilding Docs like Code: Continuous Integration for Documentation
12mAnne Gentle, Cisco DevNet | DevNet Create 2019
26mA sensible API Document Management guide
36mBuilding Docs like Code: Continuous Integration for Documentation
44mPushing documentation (so it doesn't hurt anymore)
23mTreating Documentation like Code: a Practical Account
