We also used one XSLT stylesheet per data source to insert live data into an XHTML template. I have an ultra draft article about what we did here:
http://xml.grumpykitty.biz/ As a programmer you have to be pretty comfortable maintaining XSLT, I feel, but you don't necessarily have to change it very often. On the other hand, you can create and maintain XHTML template pages easily using the various gui tools that are out there. Peter -----Original Message----- From: Andreas Bohnert [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2003 5:21 AM To: [EMAIL PROTECTED] Subject: html templates - best practise 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]
