If Discourse can host ( act as )a Knowledge Base, let’s go.
We want a tool to well organize information, to structure, to categorize the information…
Actually, Discourse put all in the same pot.
If there’s a way to distinguish an how to for Developper from an how for User, from an How to for Documentation…
If we can distinguish an " How to Contribute" from an " how to add a disk"
I ( we ?) will be happy.
Ps: Even if a knowledge base is different from a wiki, yet.
In a wiki, everybody can edit an existing document, on a Knowledge Base , not…
But it’s acceptable
Other GitHub-based solutions (as I proposed previously) are:
ReadTheDocs (Sphinx) that gives HTML/PDF/e-book output, perfect for API and manuals but could be good for any other material, i think. We already use it!
Other static web site/wiki generators, like Jekyll. Again, GitHub pages could provide the hosting. There are a lot of beautiful templates, too
I can’t stop repeating: establishing a common workflow around source control for both code & documentation has great value! Using the same tools (git and GitHub) can help sharing knowledges and exchanging informations between us.
BTW, I hope we’ll switch the issue tracker to GitHub soon!
I know what you are thinking @Jim, find the right tool is something hard to do…As I said for me http://www.nethserver.org/dokuwiki/doku.php is a draft, IF it is not efficient or not satisfying then throw it to the bin
We should have another tries with read the doc and compare. What i’m sure is I will never have reason alone.