archbee.io - has mermaid diagrams and a native diagrams block with drag and drop and the editor is great for writing documentation.
but if you need just to describe bugs, problems, and the solution, any editor would work. I would just use the simple path (even big companies just use word for some of these things)
you can use something like archbee.io since you can host the content on a domain and add a password to protect the content.
The app works similar to Confluence, except you can send the link and password for them to access the content.
archbee.io for internal knowledge base because supports Markdown shortcuts and integrates with Github to bring the content into a single place if devs prefer that
- a block-based editor that's easy to use for non-engineer people, so that everyone can collaborate in a single place
still a new solution to the market, not sure if it solves what other tools are missing.
In the end is not always about the tool, rather the culture of documenting in a proper way the knowledge.
Also, it's important for the people that use the tool to actually like using it. It makes it easier to get them into the tool and write.
There's a bunch of alternatives out there. Lately, I've seen in some Twitter threads people recommending archbee.io.
It's new and it works like having multiple Google Docs organized together, and you don't have to code anything to get started.
I am sure there are a lot of great open source documentation tools, but if you want a single tool for good text input AND diagraming I would mention archbee.io in this thread.
It has native and mermaid diagrams and a block based editor that supports markdown shortcuts. You can check the gifs on the homepage to get a feel of how it works and what it does.