Stefano Mazzocchi wrote: > Stephan Michels wrote: > > Stefano Mazzocchi wrote: <snip/> > > So, at the end, here is what I propose: > > 1) we remove all the old docs targets from the build
To remove the "build docs" target, i agree. To remove the webapp docs generation, i do not agree. > 2) documentation will be done thru forrest. This requires forrest be > available on the machine separately. since users won't update the > documentation this should not be a problem. But we do want to encourage the users to update doco and send patches. So i would not use them as an excuse. > 3) we ship the pregenerated documentation in the distribution and we > ship along the xml source files. if the documentation is included in the > webapp cocoon will simply *read* them (not process them as right now). Why would you want many megabytes of generated docs in the cvs? This seems to defeat the purpose of Cocoon. Surely there is a way for Cocoon to continue to generate its own doco via its webapp. We had some discussion about that on cocoon-docs but there did not seem to be any followup. Re: Stages of Forrest Transition http://marc.theaimsgroup.com/?l=xml-cocoon-docs&m=104847388622334 > 4) this breaks the flow samples that depend on those stylesheets but > they are going to be refactored anyway, so don't worry. > > 5) finally, remove all the doc-generation stylesheets from the CVS > > what do you think? That an xml framework that needs to deliver pre-built documentation is an old hack. --David
