We use MediaWiki + SMW &#x2F; Semantic Forms. This allows to define a data model and forms which makes it easy for user to add &#x2F; write to the wiki in a structured way - and without sitting before a blank page. For free text, the new Visual Editor works also rather well, though it&#x27;s not easy to setup.<p>The structured information can also be queried, visualized, exported to various data formets etc.<p>To document software projects, I really like to write *executable documentation&quot;. E.g. I&#x27;m using JSON Schema a lot to define my expected data structures and contracts between modules.<p>Then I write a small program that automatically generates the technical documentation based for me.  Humans can still add&#x2F;annotate to the documentation because it&#x27;s a wiki (and I can separate between auto-generated and human-generated rather easily, because of queries).<p>So far, I really like this approach as it has the automation of doc generators, the flexibility of wikis. Most of the information is stored&#x2F;accessible as data &#x2F; API. The downside of this appraoch is, that this platform takes some time and knowledge to setup and model the data structure &#x2F; forms. Without those, corporate wikis usually seem to die the &quot;one man show&quot; death you described