Categories designed

Categories can be used to organize the pages of your wiki in several ways. It is possible to assign another lay-out, other user's rights, and improved navigation to parts of your wiki. Typically, assigning and changing categories is something for site administrators, and not to be left to the users of your site.

In this respect, categories are like MediaWiki namespaces, but better and more useful. Unfortunately, they are not much like traditional categories. Your best option for categories at the present time is to use tags instead.

Wikidot combines namespaces and categories in an unusual but useful way. As with namespaces, the category is part of the url. For example :


Listing Pages by Category

Several modules have "category" as a criteria for selecting pages to list:

  • PageCalendar — lists number of new pages per year/month of the specified category ->PageCalendar Example
  • ListPages — universal module for selecting, processing and listing pages -> ListPages Example
  • Pages — module for listing pages -> Pages Example
  • PagesByTag — lists all pages, that are tagged with a specific tag -> PagesByTag Example
  • TagCloud — creates a customizable tag cloud for tagged pages (of the specified category) ->TagCloud Example

Pages can be listed by category using the Pages module.

Built-in Categories


Default is the base "category". It requires no stub. This page's url is en:categories, so it's in the "en" and not in the default category.

Nav (Navigation)

The nav category is used for the side (nav:side) and top (nav:top) menu pages: Menu


The system category is used for general wiki use, such as listing all pages system:list-all-pages.

  • There are other pages in the system category, please list them.


The forum category is used for… you guessed it… the built in wiki forum.

  • forum:start is the forum index.
  • forum:recent-posts lists the recent posts of your forum. It uses a module to do this.
  • there are probably others


The admin category is used for admin pages, of which there is only one :

  • admin:manage, the site manager

Access rights per Category

Default access rights are defined by the wiki administrator.
New categories inherit from default access rights.
Specific access rights might be defined by category.

  • admin: restricted acces rights to admins ans moderators
  • user: one might imagine that only the creator of a page falling in this category could modify his/her page (admins keep all access rights)

Themes by Category

The wiki administrator may apply different themes to different categories. Example: one could create color variations of a base theme, i.e. a pink theme for category girls:, blue theme for category boys:

Known Problems

One Category Only

Because the category is really a namespace, it limits your page to only one category. As a workaround, you can use tags.

Categories Cannot Be Nested

Because there is no category page to edit, categories cannot be nested. Instead, the pages in a category can only be listed in one big list.

Categories are Automatically Created

Whenever a url contains a namespace format with a colon, the category is automatically created. Unfortunately, while this does save time, it causes you to have to pipe link pages with a colon.

Related Pages


These pages link back to this one. You may find them helpful.

Tags: category

A category (in a wiki often called namespace) is under normal circumstances known as the first part of the page name - the partial name before the colon (:) in the page name.

Tags: address category name url

Private Categories
With the changelog of 2010-02-02 there is now a "View" - row available in the "Permissions" of the site admin available - but only for "NON _default+" categories !).

And the "landing" page" for visitors without the "View allowance" is called "category:_public".

Now it is possible to make the content of pages of a specified category "private" - visible only for specified groups of visitors:

  • anonymous or
  • Wikidot members ( logged in) or
  • Members of the wiki alone.
  • Admins and mods have always the permission to view all…

If you want an extra landing page you should name it ""(selected)xyz-category:_public" - this is a "hidden page" (the underscolre at the beginning) and it is displayed only if an "unauthorized visitor" try to reach such a "private" page.

The "landing page" can hold the relevant information like:

Reserved content

This area of the website is available to users with permission. If you'd like to access this (perhaps only wiki-internal) area, please contact site administrators.

You might already have the necessary permission — please sign in first.

See also

Other relevant (glossary)information about categories: (Category) (Soft Category)

in our Handbook - the "site manager permissions" page:
Tags: category private


(Original Page=

Templates( live)


  • template is a special page that defines common items to display on pages in a category
  • templates are easy way to change the layout for pages in a category
  • the name of the special page defining the layout for a category is category:_template (examples below)


To create a template for a category you create a page called "_template" in that category. For the default category, the template page is called "_template". For example:


Pages that start with an underscore are not listed by other modules and hidden in most cases.

Defining layout

The purpose of a template is to define a layout of pages within a category. Here is a simple template that forces the height of the content box. Create a page called _template with this code, and then reload the start page of your site:

[[div style="min-height:600px"]]

Here is a more typical template, which adds a comments module below the page content:

+ Original content of the page below



[[module Comments]]

It is easy to image what it really does. When this markup is saved as some-category:_template, all pages from the some-category will be combined with the template during rendering. Content of the page will be substituted into the %%content%% tag. This way we can add headers, side bars, navigation elements, modules and comment boxes to the template and the viewed page will automatically have it.

When you try editing a page from the category, only the "inside content" is editable. Template is applied only when viewing the compiled page.

Splitting the content

Let us start with an example of a template:




%%content{3}%% %%content{4}%%

Tags: category template


This page has to be rewritten and the include:languages has to be cleaned from [[include include:languages pagename=actualpagename]] which is not necessary anymore

This page describes the conventions neccessary for translation of the handbook into other languages (localisation).

Please - if You want to contribute any translation into your language - feel free to do so, but keep an eye on the conventions written here!

And if You have any proposals write them down in our forum here ( menu at left top ) or on the coffee table in the community forum:

The idea is to have language-dependent categories in the handbook site.

This means
all english document pages belong to the (namespace/ category) en:
all french document pages (direct translations from the english original) belong to fr:.
all german document pages belong to category de:

The "Title" can be / should be in your original language, but the url - the "page name" after he language category - has to be always in english!" Or the navigation would never find the parallel page with another language-category.

The page names itself should be in their local language, ( like fr:glossaire for en:glossary)
but (if necessary and easily possible), redirected from the direct "copied" original page fr:glossary.

The language codes to be used are defined in the ISO standard:

If you want to add another language go to en:add-another-language page!

All listings in a specific language can be done with the Pages module :

[[module Pages category="de"]] a.s.o.

The Page tags Cloud works with categories too.

The main (start) page (Welcome page) on the left side is then only the starting point into other (even english!) categories!

Typical page name for the "virtual start page of " the "handbook" in german ( german "Welcome page") :

" ! - please change the "de:" to YOUR language code (see down the link) .

Do not forget to copy the nav:side panel to your language category nav:side-xy.
Any admin can than join the (category - dependent!) nav:side-xy to the correct language-category.
And change the "edit this panel" to the correct new nav:side-xy !

The in all roots -included include:languages page should be changed to new languages too!

all languages shall have their own category, English included in order to list english tags in the corresponding nav:side.
Yes, it is possible to have one nav:side per category.
Thus nav:side-en nav:side-fr nav:side-de
- gerdami 30/7 at 20:26

French series

I just started the french series and it is really easy to create fr:pages by adding the prefix fr: and keeping the original pagename but translating the page title.
All pages should have its equivalent in the other languages. Keeping the original English name will give no problem for me to link to non-yet-existing de:what-ever-page-name.
Moreover, with the tool Wanted pages we can list easily missing pages. They are listed alphabetically with the fr: prefix. Easy.
- gerdami 30/7 at 21:37


Once a reference English page name has been chosen, it is not suitable to rename it (except from the beginning) … fr: and de: … would not be renamed automatically.
From now, the original list-all-pages lists all pages (all languages mixed) => we should now RENAME ALL English doc pages to en:pages.
Do not forget the + show dependencies !!!
- gerdami 30/7

Let us open a forum for translators in this wiki, one section per language, plus one for the reference language, and may be (I'm not sure) a per page forum.
- gerdami 30/7

Tags: category convention language localisation to_be_revised translations

Bookmark and Share

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License