Hi! I have some thoughts about the install part. First of all, we need to have a solution for that ugly file structure introduced in install files, and find final places for install files.
First of all 90% of config.xml and install.configure.*.xml files can be distributed into extension documentation files. The question is who has the time to do this, and how to do this. For now, we have mysql/reference.xml [and maybe some others] with the ini info moved into the extension reference. IMHO it would be the best to have a configure.xml and an ini.xml file in every reference dir with the corresponding configure and ini stuff. These files can of course contain the same [or similar] structure used in mysql/reference.xml This would still leave some general options. The question is where to put them, and how to handle them. As discussed before, we would like to throw in a new build script, which will generate indexes for configure and ini options for an appendix. So we can move all these general options to that appendix, and leave space there for the list of autogenerated links of more specific options. So then intro.xml install.*.xml and security.xml will be left in chapters/. We'll we previously agreed (as I remember ;), that chapters is a really odd name for this. And we also agreed on a new directory named install for general, and server related installation information. So intro.xml and security.xml is left in chapters... IMHO security is a kind of appendix, though it is much more important than to be an appendix... Intro needs some more info, the integration of php.net/tut.php is one step forward with that part... The question is how these parts will be reflected in the TOC of the manual? We need some structure for the install part, as using "Server-" as the title prefix is a not too professional way of putting sections into a part (as done now)... Thoughts? Goba
