No, i am talking about the Wiki, globally, as others users experienced the same with different topics
1 Like
Totally agree with you.
Discourse is great but search engine…not really efficient.
For me, it can be useful but the main knowledge base has to be in a wiki or something like that, for Manjaro specificities at least as well as useful tutorials.
Until last year, i was with Ubuntu and/or Debian and i always ended-up on Arch wiki for many things, this is the only place where you can find the information you need, even with other distros.
A nice and good Documentation is an advantage to increase distro’s adoption, in my opinion
1 Like
Perfect. Indeed is far from being ideal, and we all agree with that. What is the next step? (not asking from ignorance)
1 Like
Oh oh, i do not know.
First think would be not to cool people enthusiasm when they make some observations and share their thoughts.
We do. Is in the makings, but you didn’t like me mentioning how we do it and when …
Oh, but i don’t think you are a poppy to get frozen at the smallest drop of temperature in discussion … you still have the energy to argue about something that happened an hour ago 
Everybody can do that, but that doesn’t solve the issue. If someone relies solely to: Manjaro should do this and that then is not much help for anyone in the team.
1 Like
Do you realize that your intervention in this thread prevented people from giving their advice. Your first message was clear and with authority, then you closed it, then re-open…
That is exactly what i did not do. I asked people their opinion first to be sure i was not alone to think what i think.
Indeed, i am a little shivering bird, nobody’s perfect 
If people are scared by a comment made by me, then what you propose - an echo chamber just for yourself?
You did shared your observations and some complains, so did the followup comments.
I’m a person, and as a forum member i got opinions too.
One proper way to deal with this is
- point the issue
- come up with the solution
Same as you deal with a topic for someone that asks for help.
Is not working, looks bad, is incomplete, it fails, is lacking features … - are all ok remarks, nobody argues with that as a critique, but if the next step is not there, then is just talking…
Reply, is bad. Keep it silent, is bad.
1 Like
This thread is going to nowhere, therefore it better ends here.
I totally agree with this statement, However there is no need to replicate ARCH documentation.
I do agree that USER documentation needs improvement, Manjaro always has been a user driven distro and a such because the team is very small its up to the users to volunteer to write documentation, me personalty if I was to write documentation I would start by developer docs as that is even more needed from my point of view.
The issue with porting tutorials from the forum to the wiki is we need author permission, that’s makes it hard and is actually easier if the author signs in the wiki and writes there instead of the forum.
I am reopening this post in the hope that everyone gets back on topic and maybe wants to volunteer for this task or for some small bits of this huge task.
7 Likes
Nice answer, thanks.
As a former developer (not anymore since a very long time), i would say that both are important. But as a team member, i understand your point of view. Mine is a little bit different though.
Could we dedicate a section on the forum for Howtos, where you could pin a warning as first thread saying it is clearly stated that by posting in this section, you agree that your post or part of it will be reported in the wiki if useful ?
It could also be stated when users create an account here to become a member of the forum.
This kind of Howtos section already exists in “Contribution” so, it should be possible.
Sure we could post that, but it will still take someone time to move it over the wiki and quote the author to a forum name that could disappear in the future, because the user has anonymized his account or left etc.
Well, in my opinion, no need to quote him/her.
In my case, if one day i write a Howto i do not care to see my name in the Wiki. More than that, i don’t want to see my name.
How i see it is :
- A user writes a Howto on, for instance, btrfs or something else.
- This Howto is read by a team member who estimates it should be added to the wiki
- This Howto should be tested by several team members and/or by members (not necessarily team member)
- Tests have to be done on several kernels, or several DE (if applicable) etc…you get the idea, to ensure this howto/tutorial works properly.
- This Howto can be modified by the testers, if necessary, to make it better, more complete.
- Then, it’s published on the wiki when everybody is agree.
But, i would say this is not enough, for this kind of Wiki/Knowledge base/Tutorials, we also need to defines rules :
- Font used
- Format and size of the pictures/screenshots
- The level of difficulty should, in my opinion, be specified as it’s already done in the contribution section
- Grammar and syntax must also be checked
- etc…maybe an UX guy could help us to make the information appealing and easy to read
This is just some thoughts. I know you are a small team, and a lot is already done. I even hesitated to create this thread for that reason.
I think there is not need to have hundreds of howtos, as you said it, no need to replicate what already exist on Arch wiki.
wiki is best for search ? 
for me, exists too much forum “howto” on all subjects so impossible to classify in a wiki.
And a lot of howto’s are (good) personal recipes : if in wiki, users might believe that this is the official way “to do”
EDIT
And for me the “how to” are better in forum: we have in addition comments and links to topics concerning the functionality (not possible in wiki)
yes, we can include some in existing pages of the wiki (the wiki is open to all)
1 Like
I agree that some how to’s do not fit in the wiki, It has to be things specific to manjaro that are not affected by upstream changes, like Pamac is ok, but display drivers is not as documentation can change with a simple update.
1 Like
Howto / Tutorial / Walkthrough / Procedures …this is not really my point, it can be on whatever we want provided it’s useful.
Of course, what is specific on Manjaro is useful, but there is more than than.
A good start point could be to check what are the most frequent en recurrent questions and difficulties for users here.
1 Like
Yes and this is a good point.
For an experimented user, hey, he knows that there are always several ways to do one thing, so that’s ok.
For a non-experimented user, it gives him, at least, a method tested by members which works on the distribution he’s installed.
1 Like
the few pages i have been using on the Manjaro wiki has been useful, but only like 2-3 of them, i mostly find more answers in the Arch Wiki or older forum posts
Probably not relevant but I find most helpful posts when trouble shooting on the archived forum
1 Like