Documentation challenges
Two pages to look at (for discussion): FeatureX and DocConventions.
Here's my quick take on the challenges we face:
(1) The documentation is not discoverable from the tw.o menu. We need a custom menu for the documentation.
(2) Marc developed a rather complex (and I think somewhat inflexible) plan for differentiating among the various types of documentation pages (FeatureXGloss, FeatureX, FeatureXDoc, etc.). We need to decide whether we should consistently follow this or make changes. Taking a cue from Apache, MySQL, and PHP docs (and others), I prefer a more flexible approach with the following sections:
installation
getting started tutorials (admins)
getting started tutorials (users)
reference (users)
reference (admins)
reference (devels)
how-to (i.e., for setting up a new site with the features you want)
The part that Marc's nomenclature described is the reference manual (user and admin version).
(3) The various contributions need to be collated into (I think) html pages (zipped) and pdf. Perhaps the developers could write some code to output these from Wiki structures - they've talked about it, I think.
My big concern is that people are going to start writing stuff using a page nomenclature that will later require a huge reorganization.