Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
slackdocs:tutorial [2012/08/30 07:30 (UTC)]
gerardo.zamudio [Use of Discussion Pages]
slackdocs:tutorial [2013/03/12 21:41 (UTC)] (current)
alienbob [Wiki Tutorial and Guidelines] getting fed up with the "work in progress" warning if nobody is working on it.
Line 1: Line 1:
 ====== Wiki Tutorial and Guidelines ====== ====== Wiki Tutorial and Guidelines ======
-<note warning>​This page is a WIP (work in progress)</​note>​+
  
 ===== Namespaces ===== ===== Namespaces =====
  
-Please get acquainted with the concepts behind namespaces in DokuWiki: [[http://wiki.splitbrain.org/wiki:namespaces]]+Please get acquainted with the concepts behind namespaces in DokuWiki: [[https://www.dokuwiki.org/​namespaces]]
  
 ==== Plain Articles ==== ==== Plain Articles ====
Line 39: Line 39:
   * A page's main title heading should be in **H1**, the headings under that **H2**, headings under **H2** should be **H3** etcetera.   * A page's main title heading should be in **H1**, the headings under that **H2**, headings under **H2** should be **H3** etcetera.
   * Don't use horizontal rulers unless necessary (for instance they are not necessary if there is a heading right above or beneath where you want to mark a "new section"​).   * Don't use horizontal rulers unless necessary (for instance they are not necessary if there is a heading right above or beneath where you want to mark a "new section"​).
-  * Surround ​texst strings containing example commands, filenames and computer text with a "code text" markup. For example: ''​man rc.inet1.conf''​. There is a "​TT"​ button in the button bar above which will insert exactly that markup.+  * Surround ​text strings containing example commands, filenames and computer text with a "code text" markup. For example: ''​man rc.inet1.conf''​. There is a "​TT"​ button in the button bar above which will insert exactly that markup.
  
 Here is an example of what a small page could look like, using namespaces for sub pages etc: <​code>​ Here is an example of what a small page could look like, using namespaces for sub pages etc: <​code>​
Line 137: Line 137:
 ==== In English, Please ==== ==== In English, Please ====
  
-English is the primary language of the Slackware Documentation Project. This seems only natural since Slackware Linux has an english-only installer and english-only documentation. The admin team wants to prevent this project from getting stuck in a Babylonian mess.+English is the primary language of the Slackware Documentation Project. This seems only natural since Slackware Linux has an English-only installer and English-only documentation. The admin team wants to prevent this project from getting stuck in [[wp>​Confusion_of_tongues|a Babylonian mess]].
  
 ==== So How Are non-English Contributions Being Handled? ==== ==== So How Are non-English Contributions Being Handled? ====
  
-That being said, there are many valuable contributors who simply don't want to write a text in a language that is not their native language. We don't want to frustrate all these potential writers, the more so since we count on all of you for making this project happen. After some discussion on the admin list, we found a viable solution for this dilemma.  +Please check [[slackdocs:translation_guide#​creating_a_page_in_your_own_language|Creating ​Page in Your Own Language]] ​in the Translation Guidelines.
- +
-Here's an example. Let's say you're French, and you wish to contribute a HOWTO about OCR text scanning, in French.  +
- +
-  - Send a message to the ''​slackdocs@alienbase.nl''​ mailing list, asking for a translator for your language. Something in the line of"Hello everybody, I'm busy writing ​HOWTO about OCR text scanning ​in French. Can anybody translate my article into English once it's finished?"​  +
-  - As soon as you find your translator, or an editor picks one for you - which shouldn'​t be too hard, since our numbers seem to grow daily - you continue the discussion off-list, until both the text and the translation are finished. +
-  - The translated text gets published first, ​in the main section of the site. The Sources section mentions you as the author, and the translator as well. +
-  - Finally, your original text gets published in the (french) localized section of the site, mentioning you as the author again+
  
  
 <!-- Do not remove this line and the text below. Thanks! slackdocs@-->​ <!-- Do not remove this line and the text below. Thanks! slackdocs@-->​
-{{tag>​slackdocs tutorial}}+{{tag>​slackdocs tutorial ​needs_attention}}

In Other Languages
QR Code
QR Code slackdocs:tutorial (generated for current page)