cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Diana Shannon <>
Subject Re: Summary of Available Sitemap Components
Date Mon, 22 Apr 2002 15:37:45 GMT
Stefano Mazzocchi wrote:

> How can we integrate this into our documentation?

First, the future content (when properly tagged in src files) as well as 
the pipeline components Bernard has developed have yielded a wonderful 
reference guide, needed by all levels of Cocoon users.

Second, content fragments generated by this approach could yield 
time-sensitive fragments for use within additional documents. We'd need 
to provide authors with clear guidelines how to pull this content into 
their documents if/when it becomes available.

A few thoughts:

1. We might need to consider the appropriate scope of the content when 
deciding what custom doclet tags to use/require. A large number of 
custom tags could create SoC issues from a document management point of 
view. In other words, do you really want a content editor tinkering 
around with java source files?

2. I assume we'd have tags for content like action parameters and 
configuration details and their meaning?

3. We should make sure users can generate similar content/docs for their 
own custom components, particularly if they manage/maintain their code 
outside the scope of the cocoon distribution.


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

View raw message