DokuWiki

It's better when it's simple

User Tools

Site Tools


tips:tailorwikirules

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
tips:tailorwikirules [2010-09-11 16:24] – specci 117.196.147.3tips:tailorwikirules [2017-10-31 16:48] (current) – [Global] 185.57.4.67
Line 2: Line 2:
  
 This tip recommends some best-practices to follow after installing DokuWiki and before announcing and opening your WikiSite to the public. It's part of the list of [[:tips]] of DokuWiki. This tip recommends some best-practices to follow after installing DokuWiki and before announcing and opening your WikiSite to the public. It's part of the list of [[:tips]] of DokuWiki.
-===================+
 ===== Global ===== ===== Global =====
  
-  * Create a new folder under **lang** if no locale folder exists yet, as a copy of the en folder. Rename it to your **2-letter ISO country code** and change the values inside lang.php, as well as translate all raw text files to suit your needs. +  * Create a new folder under **inc/lang** if no locale folder exists yet, as a copy of the en folder. Rename it to your **2-letter ISO country code** and change the values inside lang.php, as well as translate all raw text files to suit your needs. 
-  * Edit the **start page** content to indicate the most important pages of the wiki, sorted by namespace ranking. Works like a homepage for all other major pages of your wiki. Don't forget to describe in one short sentence the main reason or objectives behind the deployment of the wiki. This start page should have an **index of all available namespaces** along with a brief description for each one. [QHow do you create an index on the startpage?] +  * Edit the **start page** content to indicate the most important pages of the wiki, sorted by namespace ranking. Works like a homepage for all other major pages of your wiki. Don't forget to describe in one short sentence the main reason or objectives behind the deployment of the wiki. This start page should have an **index of all available namespaces** along with a brief description for each one. You can use a plugin like [[plugin:indexmenu]] to automatically create an index of all namespaces. 
-  * Create a list of all available **namespaces** that describes each namespace, the top level document of each namespace, and how to add new documents to each namespace. This helps new users to understand the documentation structure in place, while avoiding a proliferation of similar namespaces just because one user doesn't know that another user has created a namespace to group documents on the same subject.+  * Create a list of all available [[:namespaces]] that describes each namespace, the top level document of each namespace, and how to add new documents to each namespace. This helps new users to understand the documentation structure in place, while avoiding a proliferation of similar namespaces just because one user doesn't know that another user has created a namespace to group documents on the same subject.
   * Create a **Quick Syntax** page tailored to your Wiki's audience. Users sometimes don't want to go through the full syntax page content, they just want to start editing as soon as possible with a minimal set of formatting rules.   * Create a **Quick Syntax** page tailored to your Wiki's audience. Users sometimes don't want to go through the full syntax page content, they just want to start editing as soon as possible with a minimal set of formatting rules.
   * Add a **Frequently Asked Questions** (FAQ) page to your wiki. This page will evolve as time goes by and will keep track of most frequent questions that users ask about the wiki site, wiki engine, and content.   * Add a **Frequently Asked Questions** (FAQ) page to your wiki. This page will evolve as time goes by and will keep track of most frequent questions that users ask about the wiki site, wiki engine, and content.
-  * Add a **Suggestions Box** page to your wiki, so users can post comments or suggestions on how to improve the Wiki.+  * Add a **Suggestions Box** page to your wiki, so users can post comments or suggestions on how to improve the Wiki. You might want to look into the [[plugin:discussion:discussion|Discussions]] plugin.
   * Add a **Rules, Conventions and Policies** page to your wiki. It should describe the content conventions of the main editors and the rules that newcomers must obey in order to add or edit content. This should be locked against editing, since it will be a static content page.   * Add a **Rules, Conventions and Policies** page to your wiki. It should describe the content conventions of the main editors and the rules that newcomers must obey in order to add or edit content. This should be locked against editing, since it will be a static content page.
-  * Add an **RSS Feeds** page to your wiki. It should describe the options to receive recent changes content through the RSS Feeder, specially if you want to inform users about how to receive changes of a namespace only. See the RSS [[:syndication]] page as basis for the content of the page in your site.+  * Add an **RSS Feeds** page to your wiki. It should describe the options to receive recent changes content through the RSS Feeder, specially if you want to inform users about how to receive changes of a namespace only. See the RSS [[:syndication]] page   as basis for the content of the page in your site
 +  * Add a template for common formats.
  
 ===== Users ===== ===== Users =====
   * Add an __Enroll-User__ page that describes a very simple and quick procedure to follow, by visitors that actively participate on the WikiSite. This procedure must explain the Access Control Level concept and how it is related to user authentication and authorization.   * Add an __Enroll-User__ page that describes a very simple and quick procedure to follow, by visitors that actively participate on the WikiSite. This procedure must explain the Access Control Level concept and how it is related to user authentication and authorization.
   * Customize the [[:signature | signature string]] that users will use for signing their content contributions.    * Customize the [[:signature | signature string]] that users will use for signing their content contributions. 
tips/tailorwikirules.1284215055.txt.gz · Last modified: 2010-09-11 16:24 by 117.196.147.3

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki