An documentation workflow loved by both Data Scientists and Engineers
summary
Describes a workflow that treats white paper text as code using Markdown, GitHub Enterprise, Pandoc and LaTeX with CI/CD and a review process to replace email/shared-drive editing and clumsy online collaboration. Explains the collaboration problems encountered and how the VCS + Pandoc pipeline let engineers and data scientists jointly produce a 50‑page document (text, diagrams, equations, graphics) rapidly, and notes remaining issues still being addressed.
AI-written summary · about
related talks
44mPushing documentation (so it doesn't hurt anymore)
35mThe practical implementation of Documentation as Code
47mDocumentation as code (explained to my dad)
47mEngineering Documentation
42mEngineering Documentation
59mTransforming your Documentation Process
26mWhy Docs-as-Code Peer Review Should be Part of your Dev Cycle
50mContinuous and Automated Documentation Docs As Code in Practice