MozillaZine

Rules/Categories

From MozillaZine Knowledge Base

(Difference between revisions)
Revision as of 11:21, 28 February 2005
Asqueella (Talk | contribs)

<-- Previous diff
Revision as of 23:17, 5 March 2005
Asqueella (Talk | contribs)

Next diff -->
Line 1: Line 1:
-: ''See also [[Rules/Templates]].''+This explains how you should use [http://meta.wikimedia.org/wiki/Help:Category categories] when editing this Knowledge Base. This is work in progress. Discuss these rules on the [[Talk:Rules/Categories|talk page]].
-There was a general consensus that using wikimedia [http://meta.wikimedia.org/wiki/Help:Category categories] is a good idea. Simple article names and good categories hierarchy will make it possible to replace pages like [[Firefox]], [[Firefox : FAQs]], [[Firefox : Tips]], [[Firefox : Issues]] with category pages. On the [[Talk:Rules/Categories|talk page]] there is a draft for categories hierarchy and related discussion.+Be sure to also read [[Rules]] and [[Rules/Templates]].
 + 
 +'''Please do not start creating categories now. We would like to have a draft, that majority agrees on, before implementing anything. Renaming categories is hard.'''
 + 
 +==Categorizing articles==
 +* Each article in the KB must belong to one or more categories. Each category except [[:Category:Top level]] must be a subcategory of one or more other categories.
 +* Generally, when an article is put in a category A, it shouldn't be put in "parent" categories of A, i.e. if you put an article in [[:Category:Issues (Firefox)]], you shouldn't also put it in [[:Category:Firefox]].
 +* A related rule: put articles into the most specific categories you can. This means that [[:Category:Firefox]] will only contain those articles that couldn't be categorized better.
 +* Each article should be put in all categories it belongs too (as many as possible). In particular, all articles categorized in one of "Issues" categories, should also be put in a "non-issue" category. E.g. problems with Firefox extensions go to both [[:Category:Firefox issues]] and [[:Category:Extensions (Firefox)]] (?).
 + 
 +===Non user support articles===
 +* Avoid adding development and other non-support articles to user support categories.
 +* ...
 + 
 +==Creating categories==
 +* Names of user support categories should follow the rules for article names. In particular, most subcategories should include application name in parentheses, e.g. [[:Category:Extensions (Firefox)]].
 +* Avoid creating/using generic categories. Use the most specific category. E.g. instead of putting an article in [[:Category:Miscellaneous (Firefox)]], put it directly in [[:Category:Firefox]].
 +* Make sure that, in a given category, the immediate subcategories have an approximately equal level of specificity (ie, we don't want Category:Cookies sitting next to Category:Settings, since cookies are not as general as settings.
 +* "Issues" categories shouldn't have a deep subcategories tree. This means, don't create a subcategory to a subcategory to "Issues".
 + 
 +==Various==
 +* "Listing" pages (like [[Firefox : FAQs]]) are to be replaced with categories. We may use the editable part of category page to provide a manually sorted listing of pages that belong in that category. The advantage here is that when we put an article in a category, we get a link to the category page for free.

Revision as of 23:17, 5 March 2005

This explains how you should use categories when editing this Knowledge Base. This is work in progress. Discuss these rules on the talk page.

Be sure to also read Rules and Rules/Templates.

Please do not start creating categories now. We would like to have a draft, that majority agrees on, before implementing anything. Renaming categories is hard.

Contents

Categorizing articles

  • Each article in the KB must belong to one or more categories. Each category except Category:Top level must be a subcategory of one or more other categories.
  • Generally, when an article is put in a category A, it shouldn't be put in "parent" categories of A, i.e. if you put an article in Category:Issues (Firefox), you shouldn't also put it in Category:Firefox.
  • A related rule: put articles into the most specific categories you can. This means that Category:Firefox will only contain those articles that couldn't be categorized better.
  • Each article should be put in all categories it belongs too (as many as possible). In particular, all articles categorized in one of "Issues" categories, should also be put in a "non-issue" category. E.g. problems with Firefox extensions go to both Category:Firefox issues and Category:Extensions (Firefox) (?).

Non user support articles

  • Avoid adding development and other non-support articles to user support categories.
  • ...

Creating categories

  • Names of user support categories should follow the rules for article names. In particular, most subcategories should include application name in parentheses, e.g. Category:Extensions (Firefox).
  • Avoid creating/using generic categories. Use the most specific category. E.g. instead of putting an article in Category:Miscellaneous (Firefox), put it directly in Category:Firefox.
  • Make sure that, in a given category, the immediate subcategories have an approximately equal level of specificity (ie, we don't want Category:Cookies sitting next to Category:Settings, since cookies are not as general as settings.
  • "Issues" categories shouldn't have a deep subcategories tree. This means, don't create a subcategory to a subcategory to "Issues".

Various

  • "Listing" pages (like Firefox : FAQs) are to be replaced with categories. We may use the editable part of category page to provide a manually sorted listing of pages that belong in that category. The advantage here is that when we put an article in a category, we get a link to the category page for free.