Choosing or Building a Doc Platform
summary
Defines a documentation platform as an end to end tool chain and compares MadCap Flare and FrameMaker style proprietary suites, wikis/knowledge‑bases, docs‑as‑code with markdown plus static site generators, and richer formats like reStructuredText and AsciiDoc. Main question is who contributes — solo writers, professional writers, developers, or end users — since per‑seat licensing and training time matter. Advises matching tool complexity to product complexity: multiple versions or editions need a heavier setup; single SaaS may use a wiki.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:04What is a Documentation Platform?
- 1:16Categories
- 1:36Option: Self-contained tools
- 1:52Option: Docs-as-Code toolchains
- 2:27Option: API Generator
- 2:39Variable: Who will contribute?
- 3:50Variable: Product Complexity
related talks
32mAbundant with life: docs beyond the wall
59mTransforming your Documentation Process
50mContinuous and Automated Documentation Docs As Code in Practice
36mTo document, or not document that is the question
25mBuilding Docs like Code: Continuous Integration for Documentation
47mEngineering Documentation
35mThe practical implementation of Documentation as Code
44mPushing documentation (so it doesn't hurt anymore)