cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Quinn <>
Subject Re: Wiki documentation system
Date Fri, 07 Jun 2002 09:37:33 GMT

On Friday, June 7, 2002, at 06:12 AM, Bertrand Delacretaz wrote:

> On Friday 07 June 2002 02:35, Diana Shannon wrote:
>> . . .
>> I agree. I think the dynamic capabilities inherent in Cocoon's
>> distribution are underutilized. I'd also like to use it for 
>> more dynamic
>> How-Tos, something that would extend existing examples.
>> . . .
> Yes, it's more about having a dynamic documentation/comments 
> server than wiki
> or not wiki (which I'm a big fan of by the way).

wiki could be one of the choices of editor

> And I think this is valid for *additions* or comments to the 
> existing docs -
> you don't want everyone to write directly over the existing docs, but
> rather adding comments/additions to them.


> So a parallel wiki (or whatever) structure is the way to go 
> IMHO, but this
> comes once again to the question of having a dynamic server for 
> the Cocoon
> web site...

But do we?

If we had something similar to BugZilla for documentation, that 
would accept emailed doc updates, then the work of the editor 
could take place on the servers set up by the users, and posted 
to the Doc BugZilla for checking and if appropriate, inclusion.

The documentation pages could be rendered (on users machines) 
with links that allow users to bring up a form to add 
comment|add patch|etc. This form would be processed on their own 
server, then sent in to Doc BugZilla.

The XML emailed to bugzilla would contain the new content, with 
an XPath expression (auto generated by the editor) to say where 
it should be included in the docs. Probably like the document() 
feature in XSLT as this allows you to specify a file path and an 
XPath at the same time.

regards Jeremy

To unsubscribe, e-mail:
For additional commands, email:

View raw message