How to successfully do documentation without a maintenance burden?

Practical strategies for keeping software documentation up to date without it becoming a burden. Key recommendations include storing docs in the repository as Markdown files (enabling versioning, diffing, and static site generation with tools like VuePress, Hugo, or Jekyll), integrating documentation updates into the code review process to ensure changes stay in sync, adopting Architecture Decision Records (ADRs) as immutable, concise records of architectural choices that never need updating — only superseding — and automating doc generation where possible. The ADR format is explained in detail, covering title, context, decision, status, and consequences fields.