Namespaces: Difference between revisions
From Freephile Wiki
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 | |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 == | ||
Revision as of 13:25, 5 February 2016
Namespaces 
| |
|---|---|
| Summary | |
| 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. |
| More | |
| Example: | setup a 'private' namespace which is access restricted so that only a certain class of user can access that space. Because MediaWiki is not a CMS, pages in the private namespace would still show up in a search. However, the content would only be accessible to the group you set it to. So, you wouldn't use this feature to setup a space reserved for the 'human resources' group, and then draft a 'layoff' announcement because although nobody outside the HR group could read the announcement, it's existence would be knowable. On the other hand, 'status-update' wouldn't give too much of a clue about what the contents were. |
There is a short list of namespaces that are built into this wiki
You can find out more about them in the w:Wikipedia:Namespace page.
You can reference a particular namespace in a link using a Compact URI (CURIE) syntax
E.g. [[Category:Development]] 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. [[:Category:Development]]
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.
