Wiki vs living documentation
Last updated August 2026
A traditional engineering wiki is a hand-maintained page library. Living documentation is a source-linked record that updates as PRs merge, tickets close, and decisions happen in chat, so people and AI agents share current, citable context.
Quick answer
Choose a wiki when you need narrative pages that change rarely and a human editor owns every update. Choose living, source-linked documentation when the system of record must track a moving codebase and remain trustworthy for onboarding, on-call, and agents.
Comparison table
| Criteria | Traditional wiki | Living / source-linked docs |
|---|---|---|
| How content is created | People write and edit pages | Generated from connected work tools, then human-reviewed |
| Freshness | Decays unless someone updates it | Tracks merges, tickets, and decisions as work happens |
| Traceability | Often none or informal links | Every claim can open a PR, thread, or ticket |
| AI / agent use | Risk of answering from stale paste | Agents query the same cited record (for example over MCP) |
| Best for | Stable process prose, handbooks | Product systems that change weekly |
When teams abandon wikis
Teams often abandon wikis because documentation fatigue sets in. See why teams abandon wikis.