For a small startup team, we now simply do this as Markdown files in our monorepo.<p>Some such Markdown files correspond 1:1 with code, and (for things like devops processes with a script component), are named the same, or with the same codename, often with just the filename extension differing. Other Markdown files have names like `ops/aws.md` and `20200713-foo-braindump-meeting-notes.md`.<p>Normally, these are in the git main branch (unless some documentation addition/change is really tied to changes in a development branch).<p>Just putting it in the repo means one fewer place people have to look (or not see) for important info. GitLab handles all the version-preserving, awareness of changes, etc.<p>I usually use GitLab Web IDE for quick changes, and my favorite file editor for bigger changes.<p>I do this after previously using wikis for key information, and decided that the monorepo is simpler, and seems more likely to be kept updated. (I previously loved wikis, and wrote an Emacs mode for one of the wikis when I used it at a well-known company, but I'm liking the monorepo approach even better for the current startup. <a href="https://www.neilvandyke.org/erin-twiki-emacs/" rel="nofollow">https://www.neilvandyke.org/erin-twiki-emacs/</a> )