Difference between revisions of "Rules for Categories"

From GhostBSD Wiki
Jump to: navigation, search
(Usage)
(Rule for this Wiki)
Line 28: Line 28:
 
We know, that the following rules are not full applied yet. But we work on it.
 
We know, that the following rules are not full applied yet. But we work on it.
  
Some category names refer to Erics naming for [[Software Station]] and [[Update Station]].  These  again seems to be related to train stations.
+
Some category names refer to Erics naming for [[Software Station]] and [[Update Station]].  These  again seems to be related to railroad stations. So we follow this thread.
  
# The top level Category is connected to the [[Main Page]] should also be named as <code>Category:Main Station</code>
+
# The top level Category is connected to the [[Main Page]] and is named <br/>
# The second or/and third level should be named <code>Central Station<code>. It depends on if there are related sub-pages and a navbar is in use.
+
<code>Category:Main Station</code>
# The next level for application lists is chosen: Category:Station
+
# The second and/or the third level should be named <code>Central Station Foo<code>. Central stations lead to other central stations, with other words: Central stations are pages with list of further lists.  
# Other categories are more related to the special tasks.
+
# The next level of category is chosen as Category:Station. A station contents lists of applications, like a "passenger list". The Category:Station we use only in connection with application lists. In relation to other tasks we may choose more task related names.
 +
# If you like to describe a special application, than this category should named after its function, special tasks, like: Category:Game, Category:Office and so on.
 
# All categories should be connected in this way.  
 
# All categories should be connected in this way.  
# All pages, templates, images, categories should be marked with category names and connected to get a hierarchy.    
+
# All pages, templates, images, categories should be marked with category names and connected to get a hierarchy. The images and icons should be categorized after its source, were the picture comes from.
 +
# The editing area of all categories should describe the function or task of this category and have to be categorized as well.<br/>
 +
The Category:Game belongs to the Category:Station <br/>
 +
The Category:Station belongs to the Category:Central Station Application
 +
The Category:Central Station Application belongs to the Category:Main Station
 +
# With this we get a category hierarchy. No page, no application, no tip and trick get lost and we get a simple way to find information we and all users are interested in.
 +
# Please: Don't forget to categorize a page. And if you have chosen a category make a note about this category and categorize it as well. 
  
  

Revision as of 04:32, 5 February 2020

Welcome to Icon Disti GhostBSD.png Rules for Categories.
Wiki Contributor Page
Rules for Design Rules for Content
Rules for Maintenance Special Pages
Rules for Templates Rules for Navbars
Rules for Categories Rules for Translation
Syntax To Do Page
Back to Icon Disti GhostBSD.pngContribution

Introduction

Categories, a software feature of MediaWiki, provide automatic indexes that are useful as tables of contents.
The “Category” namespace contains categories, dynamic lists of other pages. To facilitate this, linking directly to a category page does not output an inline link, but instead includes the page into the associated category page. So the code [[Category:Foo]] causes a category link to appear at the bottom of the page (at the bottom in the box marked “Categories”). Clicking on that link takes you to the category page, where this page is visible in the category list.

To create an inline link to a category page, you need to add a colon to the front of the namespace: [[:Category:Foo]] produces Category:Foo.


Usage

Each of the pages in the Category namespace represents a so-called category, a grouping of related pages, and contains an index for the pages of its category. When a page belongs to one or more categories, these categories appear at the bottom of the page.

The category pages themselves contain 2 parts:

  • at their beginning, an optional part may contain text that can be edited, like any other page,
  • at their end, an ever present, automatically generated, alphabetical list of all pages in that category, in the form of links. In fact, in the Unicode sort order.

Managing the category hierarchy

Categories may belong to other categories in a hierarchy. Since category pages are much like any other page, a Category tag may be added to the bottom of a category page.

It is a good idea to organize all categories into a hierarchy with a single top level category. The category structure can take the form of a tree with separate branches, but more often will have a graph structure. Generally, there should be a contiguous chain of parent-child links between each category and the top level category.

Rule for this Wiki

We know, that the following rules are not full applied yet. But we work on it.

Some category names refer to Erics naming for Software Station and Update Station. These again seems to be related to railroad stations. So we follow this thread.

  1. The top level Category is connected to the Main Page and is named

Category:Main Station

  1. The second and/or the third level should be named Central Station Foo<code>. Central stations lead to other central stations, with other words: Central stations are pages with list of further lists.
  2. The next level of category is chosen as Category:Station. A station contents lists of applications, like a "passenger list". The Category:Station we use only in connection with application lists. In relation to other tasks we may choose more task related names.
  3. If you like to describe a special application, than this category should named after its function, special tasks, like: Category:Game, Category:Office and so on.
  4. All categories should be connected in this way.
  5. All pages, templates, images, categories should be marked with category names and connected to get a hierarchy. The images and icons should be categorized after its source, were the picture comes from.
  6. The editing area of all categories should describe the function or task of this category and have to be categorized as well.

The Category:Game belongs to the Category:Station
The Category:Station belongs to the Category:Central Station Application The Category:Central Station Application belongs to the Category:Main Station

  1. With this we get a category hierarchy. No page, no application, no tip and trick get lost and we get a simple way to find information we and all users are interested in.
  2. Please: Don't forget to categorize a page. And if you have chosen a category make a note about this category and categorize it as well.