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
Next revision Both sides next revision
slackdocs:tutorial [2012/09/04 20:22 (UTC)]
sycamorex [In English, Please] Typo
slackdocs:tutorial [2012/09/12 00:41 (UTC)]
nocturnal.slacker added "needs_attention" tag
Line 4: Line 4:
 ===== 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 [[https://​en.wikipedia.org/​wiki/​Confusion_of_tongues|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? ====
Line 152: Line 152:
  
 <!-- 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)