Documentation Taxonomy: Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 53: | Line 53: | ||
# XSLT | # XSLT | ||
# XUL | # XUL | ||
Revision as of 23:18, 7 March 2005
Status
This page is currently a very early scratch-pad for working up a documentation taxonomy.
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.
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.
Or at least that's my current working theory. I'll know more after I've had time to mess around with my testwiki.
PLEASE feel free to modify the list below -- I'm still familiarizing myself with some of the technologies involved (and am cribbing wildly off lists I've found in various places). Some of the following may need to be split into separate topics, or some nested within others, others just deleted or added.
Potential Topics for Namespaces
- Accessibility
- AOM
- Cross References (questionable for this level)
- CSS
- DHTML
- DOM
- Embeddable Mozilla
- Extensions
- Gecko
- HTML
- Image Handling
- Java
- JavaScript
- Layout
- Mozilla as a Platform
- Mozilla Hacking
- Necko (?)
- NSPR
- Open Source Development
- Parser
- Plugins
- RDF
- Remote Applications
- Scripting
- Security (?)
- Testing (QA, etc)
- Themes
- Toolkit Apps
- Tools
- Web Standards
- XBL
- XML
- XPCOM
- XPConnect
- XPIDL
- XPInstall
- XSLT
- XUL