cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Diana Shannon <>
Subject Re: [RT]: One step for a minimal Cocoon
Date Mon, 01 Jul 2002 11:55:45 GMT

On Monday, July 1, 2002, at 07:36  AM, Piroumian Konstantin wrote:

> For simple samples (e.g. 'hello world', 'svg') this file can be the
> front-page, and then it's worth it. But the samples with their own 
> layout
> and styles would like to have their own front-page (i18n, flow).
> So, I'd like to use a description from the sitemap for the page with the
> samples list and samples should provide a default matcher displaying the
> desired front-page.
> If you explain what else can be added to the sample.xml document 
> except a
> short description then I'll change my opinion.

We still need to treat (and manage) samples consistently (from a CMS 
point of view), regardless of their internal "skins" -- or even front 
page. "Dynamic" samples may need to be managed similarly to static 

You may need to add
  - short as well as long description content (i.e. with block elements)
  - implementation-specific info (some of the *same* samples have 
slightly different implementations, based on where they are located, 
e.g.  2.0.3 versus 2.1) This is critical info, IMHO.
- versioning info (when samples change, users may want to know. I know 
*I* do)
- topic info (so you can add links to samples from static docs in a 
How-To or tutorial, or some other doc ... )
- component dependencies (what needs updating when something in source 
- targeted user info (beginner, intermediate, advanced)

etc. etc. etc.

Does this help to convince you of the need?

-- Diana

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

View raw message