----- Original Message ----- From: "Stefano Mazzocchi" <[EMAIL PROTECTED]>
> 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. --- 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]
