documentation category ideas

[Karsten Wade]

I think this is a summary of the ideas we had on IRC on how to use
[[Category:Documentation]]:

0. Pages belong in the category or a sub-category because they
   document something.  How to do something, what something is, why
   Fedora uses something.

1. Mainly it is a parent-category.

2. Actual pages are usually in one or more sub-categories that are an
   area of documentation.  Examples: Policy; Proposal; Conference;
   Application/Program;

   [[Category:Draft documentation]] is clearly a sub-category of
   "Documentation".

   A sub-project might also put documentation that covers their area
   of the project in their category.  For example, [[Category:QA
   Project documentation]] would also be in the [[Category:QA
   Project]], just as [[Category:QA documentation]] (for the general
   public) would be in the general interest [[Category:QA]].

Questions:

* What are some further ideas for sub-categories?

* Do we want to follow a prescriptive or natural language naming
  scheme for the sub-categories?

  For example:  For several years I have been putting pages in
  [[Category:How to]]:

  https://fedoraproject.org/wiki/Category:How_to

  Looks like others have picked that up.  When I say prescriptive, we
  would want that to be [[Category:How to documentation]].  Natural
  language would leave it as "How to".

  How does this look for other ideas?

  "Policy" vs. "Policy documentation"
  "FUDCon" vs. "FUDCon documentation"
  "Application" vs. "Application documentation"
  or even "Koji" vs. "Koji documentation" (which could be a
     	  	     	   		   sub-category to "What is"
  					   and "How to" categories.)

cheers - Karsten, wiki troublemaker
-- 
name:  Karsten 'quaid' Wade, Sr. Community Gardener
team:                Red Hat Community Architecture 
uri:               http://TheOpenSourceWay.org/wiki
gpg:                                       AD0E0C41