Two products that I have seen rising in Knowledge management domain (Personal and Team ) are

Notion : https://www.notion.so/
Notion is something that I use on a Daily basis and within a month we have replaced more than 6 saas offerings with just Notion.

Guru : https://www.getguru.com/
The traditional concept of a knowledge base or “wiki” is becoming obsolete. Next-generation products unify information and contextually deliver knowledge directly into existing workflows. Guru is one company that has emerged as an early leader in this space.

There are a few things to balance with documentation:

• Making the content easily reusable by support teams to speed up replying to tickets
• Publishing the content online to anyone searching for the product plus the issue online
• Letting anyone in the company add/update/edit documentation to keep it generally fresh

The easiest way to accomplish the first is to use the documentation tool built into your help desk or customer support tool. So if you’re already using Salesforce Service Cloud, Salesforce Knowledge might make the most sense. If it’s anything like what Desk’s documentation tools were like before it was acquired by Salesforce, it should get the job done.

Otherwise, you can publish Confluence wikis publicly, either as read only or as an actual wiki that your customers could help edit (though that seems like it could get messy fast). If you already are writing internal documentation in Confluence, that may be your easiest route. One downside here though is that you can’t use custom domains with Confluence’s cloud app yet, so you would need to have your documentation on a separate domain (which works fine from an access perspective, though doesn’t help your company’s SEO rankings as much as having documentation on your domain could). Or, in the same way, you could expand your use of Paligo to cover non-technical documentation.

Essentially, if not adding new steps and tools to your team’s workflow is most important, any of those options would keep documentation inside stuff your team is already using. There’s no perfect solution, and frankly any CMS could be used to publish documentation (including a WordPress or Ghost blog, if you wanted, or any of the many documentation-specific tools), but using something you already are using and just adding extra processes around publishing could be the fastest way to get started.