Creating a content pipeline for
summary
Claims a reproducible upstream → downstream pipeline that single-sources content and automates releases: AsciiDoc attributes and include statements produce different inline and block content, Antora combines multiple content sources and uses an extension to aggregate many small files into one AsciiDoc file, CI converts AsciiDoc → HTML and runs HTML tests, and a single metadata change plus a branch triggers a release. Replaces ~300 lines of bash with a few YAML lines and two small scripts. attributes and includes enable variation, collector/extension handles add/remove outline changes.
AI-written summary · about
chapters (21)
- 0:00Content pipeline challenges
- 1:11Content reuse strategy
- 3:01Upstream vs downstream content
- 5:29Content variations
- 7:39Modifying navigation and pages
- 9:05Documentation workflow
- 11:33AsciiDoc attributes and includes
- 13:20Multiple content sources in Antora
- 15:07Component versioning
- 17:26Simplifying downstream with Antora
- 19:37Benefits for writers
- 21:50Antora search and validation
- 22:36Custom content extensions
- 25:06Content modification options
- 25:48Atlas extension for subsets
- 28:01Q&A
- 28:23Rebuilding pipeline
- 34:42Downstream compatibility
- 35:45Onboarding writers
- 39:16Automated checks and IDE
- 40:46Summary
related talks
44mPushing documentation (so it doesn't hurt anymore)
35mBuilding Docs like Code: Continuous Integration for Documentation
40mDocumentation Communities: Sound Strategy or Documentarian's Gambit?
47mEngineering Documentation
40mThe Rocky Road to DocOps
20mDevelop Pipelines as Code
50mContinuous and Automated Documentation Docs As Code in Practice
28mProject 42 - Making CI/CD a First Class Citizen in...