Malcolm's working on this as a background task and needs to keep notes or else will forget what he's done, so here they are.
As stuff gets done it gets marked with 'OK'.
</fieldset>
<fieldset><legend>Migrating the old doc trees to one new one</legend>
<p>
There are a number of doc directories scattered around the ZMap source tree and most are unused. We aim to clear these out and put all the documentation in the ZMap/doc/ directory tree and provide an HTML interface in this directory to help developers find the information they are looking for. All these files will be in the CVS and as such available to developers. At present there are no plans to host new files online (although page design allows for that possibility).
</p>
<p>
A new directory <b>ZMap/doc/Design_notes</b> will contain documentation of the various ZMap modules and further notes about how they interact and work. As work continues on ZMap design documents will be added to these files - these can be written in Open Office (eg if we wish to circulate them) and then exported as HTML once complete (which will allow easy cross referencing) or the location of the file noted.
</p>
<p>
A front page <b>ZMap/doc/index.shtml</b> will reference existing directories and provide some guidelines on where to find things. Here we are concerned with documentation accessable as part of the ZMap Source tree and not online data. The design directory will contain files generated by a script (to create a menu sidebar) and as such it's structure is constrained by how clever the script is.
</p>
<p>There is some documentation online at intweb.sanger and the source of these is in the <p>ZMap/web directory</b>. Those files that correspond to online resources will remain as is. ZMap/web sub-directories that look useful will be copied to doc/ and included in the index (most will be edited to the new format but on a temporary basis can simply be copied and added to CVS). The existing web/ files will be left untouched as they are in the CVS as simply removing them may cause build scripts to fail.</p>
<p>
After this process all the online help documentation with the exception of doxygen generated files will be available via hyperlinks to copies of these files in the doc/ directory tree, and the online data will become static. After this we can update online documentation (if desired) by copying files to the web directory and running a new build script.
