Imho a tag must categorise a content you need and you are looking for.
So vpn,webapp,apache,mysql, and much more like installation are good tags but i’m not sure concerning tag about levels (novice…middle and experimented.)
From my point of view any howto must reach the goal of the reader…even for a beguiner.
Edit:
Who can help to make Howto for dummies?
I think to have
how to setup a DHCP Server,
how to put a rule ( Red, orange, green ) on a interface,
how to configure the proxy
Such stuff can be very helpful for newcomer and for a first approach for someone who just discover NethServer and investigate possibilities.
Edit 2: do you think it can be useful to add the level? ( beginner, intermediate, advanced )
Edit 3: @sitz Can I copy paste your howtos for dummies from Discourse to Docuwiki?
At the same time, with the actual classification, there’s the category “For dummies” where we will put all tutorials for newcomers, novices…
I’m not sure ( anymore ) that’s a classification by skill level is necessary…
It’s possible to create a third tag, but is it useful? What is your point of view?
In the HowTos ( for users ), I created tags like ht_installation, ht_dummies, etc,etc… for classify these howto.
What do you think to create tags like htd_esmith, htd_webgui, htd_rpm, td_tips, htd_language for classify all howto for developers ( and futurs advanced users) in this page?: ( htd for How To Development ) http://wiki.nethserver.org/doku.php?id=developer
Edit:
I was asking myself: Must we stay with “HowTo” or go for “user guides” ( as opposites as “Developer Guides”)?
Like the ClearOS documentation, https://www.clearos.com/resources/documentation/clearos/start
we will have all the guide…
But what about a FAQ for the newcomer and the potential interested user.
Must we extend to a Knowledge base? ( Hardware compatibility, etc, etc…)
Already some how-to in the community, but we are here to help. this week I will be reviewing the new languages and new members who want to help translate.
I think the translation is a big part, and must have it’s own page.
The same tough for the Quality team.
To show the stuff, to explain how to do, to make the convitation to participate.
Administrator manual ( link to the actual Official Admin Manual )
User Guides. ( link to the actual user howtos )
Bug reports. ( link to the actual Quality page )
Contributors
User Guides. ( internal link to user guide writer at the end of the actual howto page )
Translation. ( Internal link to translation page at the end for translators )
Quality. ( internal link to the quality page at the end, the contributor part )
Developer ( link to the actual developer page)
Edit:
For futures purposes, I plan a FAQ entry in the left menu, in User Guides.
For all informations, for people that just discover NethServer and not install it yet.
For futures purposes, I plan a Knowlefge Base Entry, in the left menu, in User Guides. For all very usefull informations that all NethServer sysadmin must know.