I second this.
We already have everything, we have user accounts in place, we will have only one place for everything, we can begin to write docs NOW.
When we will find the perfect wiki, we will move contents there.
I’d also like to modify the landing page of www.nethserver.org according to Jim’s suggestions.
I just wrote my first page, see Contribution sections here:
I think ReadTheDocs and the wiki has two different targets.
The first one is for the official manual, the second one is for contributions.
Because we used it only for temporary developer documentation.
What kind of contributions? Are you meaning NethForge RPMs?
…that is a very rare beast! Never seen so far
Just for the record, currently Discourse worked fine for our HowTos, that’s a fact. We have a bunch of howtos here, don’t you think?
Most people are using it, check also:
@stephdl from your point of view, what Discourse lacks to became a useful wiki? Please, my memory is short 
Automatic table of contents? What else?
Automatic wiki-mode setting of new pages/topics?.
Easy page linking?
Discourse is cool and useful, but it’s definitively not a good platform for howtos and doc
Maybe you’re right but 55 different howtos from many people are a fact, isn’t it?
The fact is that It has definitely shown to be easy to use, handy and straightforward.
Also, people can comment below trying to continuously improve the doc.
It’s fragmented maybe, it hasn’t a good structure yep, it hasn’t basic (like TOC) and advanced features maybe, but the fact still remains 
Hmm… if there is no other option than to put it in Discourse, it is not strange those howto’s end up there… 
I do see the split between wanting to have everything centralized and needing options that are not available (yet) in Discourse.
The other option is to stick with mediawiki and maybe enhance that with some (eye)candy like http://bluespice.com/
@zamboni is right, a wiki is a book that you can follow/discover chapters from the table of content, discourse displays the last content and you find them by key word if you know them? ([of course at first you have no idea what to search][1]).
more over discourse cuts the page content, redmine no, github yes…I love to read a howto on my three 27’'.
yes yes yes
I need to have a go on the page linking by category in redmine I hope it is feasible, it must be a basic feature
From my point of view discourse should be a support forum, and all howto, bug report should be done elsewhere. (recall do one thing but do it well).
I’m a wiki player, [this is who I’m][2], Trying to explain why a wiki is better than discourse for howto is like walking for a homo habilis
For all howto there in discourse for me it is not a problem, now the most important and hard thing to do is in front of the community
[troll mode on]
Using Discourse for documentation is like: http://itechthereforeiam.com/wp-content/uploads/2014/09/right-tool-for-the-job.png
[troll mode off]
and this is clear since the beginning…
sometimes people should really listen to the suggestions coming from experienced users…
I repeat myself: the web2.0 approach is wrong in a professional environment… you can buy an ebook, but sysadmins and developers still buy books made of paper.
now it’s up to who decide to choose between the bell & whistles approach and the professional one
last post of mine here
I like to print the doc
even if the formatting features are good it seems to lack category feature, funny it is asked since a relly long time
and probably more
did I miss something ???
i’m sorry, but i must admit i’m a little lost… so just to do a recap, if i understood correctly possible solutions are:
if this is correct i agree with @filippo_carletti, unless there are a real short -term plan from devs to move issues from redmine to github… in that case leaving redmine active only for wiki maybe it’s not a great solution… i don’t wanna open a new thread about “issue on github” but i think this is a thing to know/evaluate to take a good decision…
and what will be the workflow? i mean… redmine will host all wiki? or redmine+discourse? or (i hope not) some on discourse and some on redmine?
@alefattorini it’s hard to implement a kb like this in discourse? not a wiki but could be a middle way solution…
https://meta.discourse.org/t/using-discourse-to-host-a-knowledge-base/34036/7
http://community.quickfile.co.uk/c/knowledgebase
after all it’s hard to admit, but i’m “old inside” (well also outside 
) moinmoin/dokuwiki/mediawiki are still more familiar to me…
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:
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 undertand now what you tried to explain…
With Sphinx/Readthedocs, we could have a well know ( for you ) tool.
A standardized web page, no template to maintain, there’s already one.
A when I give a look to the administrator manual… there’s no Pull Request…dx
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.
let’s have a go on http://www.nethserver.org/dokuwiki/doku.php and report your feelings
I’m completely in agree with you!
Github wiki is designed for coders only. People who want to make games- Github says to the wiki makers no you can’t help them.
