Content as code, technical writers as developers
summary
Kyma keeps docs in the same GitHub repo as code, writes content in markdown, and uses Gatsby to rebuild the site on each merged pull request so documentation ships with features instead of lagging behind. Pull requests render as a pull-request preview and pipelines run tests such as dead-link checks. Information developers create and review docs like code, manually write most content (CLI flags are auto-generated), and report that this workflow shortens documentation backlog, improves QA, and boosts community response.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:56Overview of Documenting for the Open Source World
- 7:47Publishing the Documentation
- 17:09Pipelines
- 17:54Pull Request
- 27:12Community Management
- 29:13Release Notes
- 31:11Summary and some Takeaways
- 40:00Do You Recommend Having a Separate Repository for the Documentation
related talks
47mEngineering Documentation
42mEngineering Documentation
35mThe practical implementation of Documentation as Code
35mBuilding Docs like Code: Continuous Integration for Documentation
24mDevelopers: write code, not content
25mBuilding Docs like Code: Continuous Integration for Documentation
35mFrom Code to Clarity: Collaboration with Devels when Writing Product Documentation
26mWhat you get when you invest Non-Docs time in Docs tools