Namespaces: Difference between revisions

No edit summary
No edit summary
Line 1: Line 1:
{{Feature
{{Feature
|explains= Special:PrefixIndex
|explains= Special:PrefixIndex
|description= Using the namespaces feature of MediaWiki, you can setup areas that segregate content.  Although MediaWiki is not a CMS designed for roles and access permissions, it nevertheless can be useful to segregate content in a wiki that should be 'nearby', but not in the same space.  An alternative to namespaces is to setup a "wiki farm" where each group or product, or purpose has it's own individual wiki, all running on a single software instance to reduce administrative overhead.
|description= Using the namespaces feature of MediaWiki, you can setup areas that segregate content.  Although MediaWiki is not a CMS designed for roles and access permissions, it nevertheless can be useful to segregate content in a wiki that should be 'nearby', but not in the same space.
|notes=
|notes=
|tests=
|tests=
Line 15: Line 15:


E.g.
E.g.
<nowiki>[[Category:Development]]</nowiki> will link to the page 'Development' inside the Category namespace.  Built-in namespaces are also tied to built-in functionality so for example an 'Image' link inserts that image into the page.
<nowiki>[[Category:Development]]</nowiki> will link to the page 'Development' inside the Category namespace.  Built-in namespaces are also tied to built-in functionality so for example an 'Image' link inserts that image into the page.  And the 'Category' namespace is tied to the functionality of tagging an article as belonging to the category.  So, to actually '''link''' to the category (or image) you would place a ''':''' (colon) before the prefix.  e.g. <nowiki>[[:Category:Development]]</nowiki>
 
== Alternatives ==
An alternative to namespaces is to setup a "wiki farm" where each group or product, or purpose has it's own individual wiki, all running on a single software instance to reduce administrative overhead.


== See Also ==
== See Also ==