This is the assessment I have, EVERY way to manage documents or knowledge or whatever is about as ~80% as good as the ideal solution at worst. This is a problem you can spend a lot of time bikeshedding and where it's questionable to not just use the path of least resistance tools that you already have at hand.
The #1 actual problem and differentiator all these tools has is search. The #1 thing you can do in my experience to make your documentation higher quality is to template it and make it consistent as this makes it far easier to quickly grok.
Structured documentation is such a benefit toward this, and also such a controversy within teams.
Aside from the many standards for structure and the challenges of info architecture, there are a surprising number of technical writers who are hard to convince, or cannot be convinced, to write within any sort of structure or template. Either they have to be sold on it constantly, or cut loose or moved away from product docs and toward blogs or training materials.
A writer who can not only work within a structure but also can appreciate and leverage it is incredibly valuable to a docs team, and I believe the pipeline that develops candidates for technical writing doesn't prepare folks for how much weight this carries.
The #1 actual problem and differentiator all these tools has is search. The #1 thing you can do in my experience to make your documentation higher quality is to template it and make it consistent as this makes it far easier to quickly grok.