hi addreas we are working on that direction one year ago
the idea is: .xhtml template file (with some extra tag that get content from specifics blocks) .xml content file .xml block file (blocks with content) 1. all this files aggregation into one .xml 2. xsl trasformation to put content in the right places in template 3. xsl transformation to produce the final html (xhtml) so we have a template / content seperated web site building mechanism i think that this is perfect for small to medium web sites we call this project othello and will be announced next weeks if you want to have something now (very alpha contact me directly, it will be open to anyone) --stavros wOn Fri, 3 Oct 2003, Andreas Bohnert wrote: > Hi, > > i read a lot of tutorials and docs about cocoon and i really like it, but I still > don't know, what's the best practise to handle html templates. > > I get the static part of my html page from a html designer and I want to leave it > untouched, so the designer can modify it later on. Of course, some place holders and > template instructions should be in there, to put the dynamic part into the right > place. > > maybe this strict seperation( html design <-> java/xml programming) is against the > philosophie of cocoon, because I understand: > all required data (static+dynamic) should be put in the xml datasource with the > generator and during the transformation process this data will be mixed with html(or > wap or pdf) language specific parts. > > so, how do you handle this? > any suggestions/comments are welcome!! > > thanks very much > Andreas > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
