cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan Michels <step...@apache.org>
Subject Re: [vote] Forrestizing Cocoon and more
Date Wed, 26 Mar 2003 10:30:09 GMT

On Wed, 26 Mar 2003, Jeff Turner wrote:

> On Wed, Mar 26, 2003 at 11:08:39AM +0100, Stefano Mazzocchi wrote:
> ...
> > Moreover, to be honest, I think that we should aim to improve
> > forrest/lenya and make it a structured wiki and setup a CMS and point
> > users to that for editing.
>
> Getting the latest Chaperon updates was a major impetus for the recent
> Cocoon upgrade.  Wiki parsing is just waiting for a volunteer.

;-) First we make the transition, then I will help you on this topic.
deal?

> > that's the only way they can help up writing docs because our current
> > xdocs-patch workflow is too much a stinking pain in the ass.
> >
> > >>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.
> >
> > yes, there is: ship forrest skins and xml/xslt machinery with cocoon.
>
> I'm attempting that now (a 'forrest' block).

Doh!

Stephan.


Mime
View raw message