As others have said, just dive in. If there's no legacy tool in place, getting started is easy -- spin up a docker image of Wiki.js, an instance of MK docs or w

As others have said, just dive in. If there's no legacy tool in place, getting started is easy -- spin up a docker image of Wiki.js, an instance of MK docs or whatnot, set up a backup methodology and you're off to the races. The challenge with wikis is always long-haul maintenance and relevance. Information rot and information overload, at scale, can quickly overtake the value of the effort, so understand what you're potentially getting into.