Last place I worked (about 15 people), we needed a knowledge store. So I set up Mediawiki, mainly because I know Mediawiki, and I like wikis. It started filling

Last place I worked (about 15 people), we needed a knowledge store. So I set up Mediawiki, mainly because I know Mediawiki, and I like wikis. It started filling up with articles: about the dev tooling, the servers, the services and how to use them, deployment processes and so on. New people were onboarding every few months, and it was definitely useful to have the knowledge recorded somewhere. What I didn't do is to design a knowledge schema. At what level of granularity should an article be? What umbrella topics should act as portals to articles? This is hard, and with Mediawiki it would be impossible to enforce anyway. So the knowledgebase grew like Topsy ("I just growed"), and had no structure. I set up the system because I was (part-time) the sysadmin, and my skull was rapidly becoming a repository for a lot of technical information about how the systems worked. My memory is not so good, and I needed to pickle that information before I retired. So a lot of the initial articles were created by me, as fairly detailed "note-to-self" articles, and how-tos for my colleagues. In retrospect, I suspect a tool other than Mediawiki might have served us better; but I was in a hurry to scratch my itch, and I had other duties. I think a more opinionated note-taking tool might have enforced some kind of knowledge schema. Mediawiki isn't good for representing knowledge as a hierarchy, in particular. I don't know much about note-taking tools, so I still have no idea what alternatives there were. In the event my colleagues did use the wiki, both to recover knowledge and to store it. From that point of view it worked; knowledge was being saved and retrieved. But even a collection of text/plain files would have been better than nothing; the wiki wasn't used because it was good, I think, but because we needed something. So I'm suggesting that if you have nothing in place, then almost anything is better than nothing. Whatever that something is, it should be able to export stuff in an easily-parsed format, so that you can import it to a better system should you decide to migrate (a collection of text/plain files would seem to fit that bill). I'm not offering advice, other than to try something more opinionated than a wiki. I'm really offering anecdata.