canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906
edits
mNo edit summary |
mNo edit summary |
||
| Line 5: | Line 5: | ||
== Purpose == | == Purpose == | ||
The purpose of a documentation taxonomy is to provide at least a single, comprehensive, core conceptual structure to the documentation set we will be producing. Right now the structure is extremely flat -- this is intentional, as the various technologies listed below tend to cross our "audience" borders regularly. | The purpose of a documentation taxonomy is to provide at least a single, comprehensive, core conceptual structure to the documentation set we will be producing. Right now the structure is extremely flat -- this is intentional, as the various technologies listed below tend to cross our "audience" borders regularly. I'm leaving the "root" node off here and listing the rest in discrete topics that are supposed to be relatively self-contained. | ||
I'm thinking that eventually a high level of the taxonomy (not the root, but one or maybe two levels down) will be used to define some custom namespaces within the wiki. Without having to do any hackery, MediaWiki will support up to 50 custom namespaces (plus 50 related Talk namespaces, for 100 total). The namespaces will provide flexibility and some basic structure than we would have within a single namespace. | I'm thinking that eventually a high level of the taxonomy (not the root, but one or maybe two levels down) will be used to define some custom namespaces within the wiki. Without having to do any hackery, MediaWiki will support up to 50 custom namespaces (plus 50 related Talk namespaces, for 100 total). The namespaces will provide flexibility and some basic structure than we would have within a single namespace. | ||