[neilv]

Over the decades, I've set up many engineering and organizational document processes, and I've also been a developer on doc tools. The culmination of all of this is that I've ended up gravitating to very-low-friction, tracked, centralized doc -- code-embedded API docs and Markdown files in the/a repo -- and sometimes also a Wiki (preferably a Wiki of the same platform that hosts the repo, unless you've made it hard for non-developers to access the repo platform).

But, if I absolutely have to, I'll endure Confluence. Only if people agree to stop throwing away important information into a dozen different other SaaSes and tools that are effectively write-only, as far as the organization is concerned. Don't just turn those 12 memory holes into 13.