Jeff Turner wrote: <snip/> > > I've also added Cocoon to the Forrestbot run, regenerating every 4 hours: > > http://forrestbot.cocoondev.org/sites/cocoon-site/index.html
Brilliant ... run Forrest, run. > However as the Forrestbot doesn't provide an opportunity to copy > sitemap.xmap.forrest05 to sitemap.xmap, the FAQs and some .txt links are > broken. > > So how about we: > - Rename sitemap.xmap.forrest05 to sitemap.xmap in CVS, thus making the > Forrestbot output "committable". > - (optional) Fix the Cocoon 'build docs' target to read its sitemap from > another file, so the old doc generation process still works I think that this is a must. Step by step. Cocoon can then continue to build its own docs as well. Next we can move Cocoon to using document-v11 DTD and stylesheets. > - Switch on Forrestbot's commit facility, so any committer can > regenerate and commit the updated HTML/PDF from the web interface. That would finally give us quick turnaround to publish the website. That is a milestone. Of course we have a bit of polishing to do yet, but that is why we have the staging server at cocoondev.org > This way, people doing serious doc generation can obtain a Forrest > snapshot, and everyone else can rely on the Forresbot to view updates > (updates can be triggered manually), and potentially commit the results. Yes i think that this is the simple build solution that we are looking for. Cocoon can still build its own docs via the webapp etc. and even apply its own style (or sync with Forrest) and Forrest can also build Cocoon docs. > Sound decent? Yes. Thanks Jeff for cutting through with such brilliant solutions and thanks to all of us for getting this far. --David
