> > > I don't like dynamic sitemaps and read my next mail to understand why. > > > > Moreover, nobody ever could come up with a meaningful example that > > *required* the use of a dynamic sitemap. > > > > But maybe you can. I'm all ears. > > > > To me (and I am sure others) there are 3 phases and 3 sites/VMs to > developing a website et al: > - dev.site.com > - qa.site.com > - live.site.com > > I think it would be good if cocoon could handle these. For dev, the team is > usually small and would work most efficiently if everything was able to be > dynamic (and used a storyboarding tool to layout the site :). qa and live > would be exactly the same and compiled. Perhaps dev and qa are supposed to > be on one machine and live is on your big machine.
If I get you right, what you are describing is something like an adminitrative interface for the sitemap. Something like that is available in Jakarta Struts - you have special administrative URLs where you can add/delete an action, form bean, etc. I think that something like that is possible with Cocoon too. If you need a dynamic sitemap at runtime then you can use selector to dynamically select processing paths, you can use more generic pipelines, etc. Look at the <map:mount /> - using it you can achieve something like a dynamic sitemap. > --- > It would also be nice to have promotion abilities. Perhaps by reading the > dynamic properties set[1] during the dev phase the system determines when > the site is promoted to qa, then to live. > > best, > -Rob > > [1] Properties set through a gui like: > - authors signing off on individual content pieces > - editors signing off on pages > - producers signing off on folders/sites > - etc > when all these are set to 'go' or something the site is preomoted to the > next level. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
