Bureaucrats, confirmed, Administrators
4,558
edits
Changes
Jump to navigation
Jump to search
Add quick outline of the Level10 system
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. 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>
== Usage ==
The [[MW:BlueSpice|BlueSpice]] distribution uses the [[MW:Extension:NSFileRepo]] extension to semi-protect files according to namespace.
In QualityBox, we're interested in creating an extension called Level10 that would allow for editing content in 10 separate namespaces for 10 separate levels of focus. The idea is roughly the following:
# concept - term only - defined in one sentence
# marketing - in words most people can understand
# user - in words relevant to wiki usage
# design / layout / interface - how the concept is manifest, or manipulated in the UI
# developer - how the concept is related to code or implemented in code
# test - how the concept can be tested across updates or new feature implementations
# demo - where can the concept be seen in action
# admin - how the concept can be manipulated by a sysop in the UI, or console
# system - how the concept is implemented at the system component level - dependencies or alternates
# architecture - how the concept fits with the overall system architecture
Viewing content in any level would automatically include links to the other levels.
== Alternatives ==
