[lorinab]

Running a technical session on why documentation systems fragment at scale and what actually prevents it. The problem: Most tools optimize for writing, not surviving. After 3-4 years, you get 20-30% broken links, orphaned pages, and teams asking "where did we document that?" Navigation breaks around 1k pages because hierarchies reflect how one person thought about the problem in 2022, not how new people need to find it in 2026. What works: Structured content with metadata (so you can rebuild navigation without rewriting), explicit ownership and review cycles (treat docs like code), and content/presentation separation (because how you navigate should evolve as the org grows). I'll cover the technical architecture using XWiki as the reference (LGPL, built since 2004, handles 100k+ page deployments). Real examples: University of Lorraine migrated 145k pages with full history, KIT moved 9,431 pages from Confluence. For: DevOps/sysadmin folks dealing with runbooks, internal wikis, or infrastructure docs that need to outlive team turnover. Free webinar, recording posted after: https://xwiki.com/en/webinars/XWiki-as-a-documentation-tool Interested in what others have seen work at this scale. What's your approach for keeping technical docs usable after years and multiple people leaving?