We used to use a Mediawiki wiki, which only I would edit. You kind of have to be comfortable with mediawiki syntax (does the job for everything but tables, which suck). So we moved to Confluence, which has a WYSIWYG editor, to encourage more people to document things, upload documents, so on and so forth. Again, I am the only one editing it... so our documentation is &quot;very occasionally write something down, and store it on your laptop or in your private google drive, then spend ages searching for it when someone asks&quot;.<p>So whenever a new staffer comes along, I get asked to give them wiki access... but I&#x27;m the only one here that uses my edits (only ops staffer). Sure, have some wiki access, for all the good it will do you!<p>I really don&#x27;t recommend our model :)<p>Anyway, this is an important point: <i>documentation is not free</i>. It takes time. Even shitty documentation takes time. If you want good documentation, you need to budget time away from other tasks. When I used to work in support, the field repair engineers would budget 30% of their hours for doing paperwork - not <i>documentation</i> specifically, but it clearly shows that &#x27;writing stuff&#x27; is not something that springs as a natural&#x2F;free parallel to other activity.