Hi Alex, i haven't think about xhtml. I will have a look at it! We don't have an agreement, how to specify the dynamic parts. I'm used to tapestry, which is perfect to work with html templates, but we need to create different outputs (wap, pdf, html) so cocoon would be very nice! I think i would mark dynamic parts with span or div tags and replace this sections during transformation. But I'm not happy with that.
I was also thinking about velocity, but as far as understand (from some postings) cocoon would just produce velocity output. So I could not use a velocity template during transformation. But maybe I'm wrong. Do you know more about that? andreas ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 03, 2003 11:30 AM Subject: Re: html templates - best practise > [EMAIL PROTECTED] 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 > > Is it possible to get the designer to generate xhtml templates instead? > It might be just a flag in his html design package. > > How does he specify which bits are not static? Does he put some psuedo tagging in there like > > > XXXXX INSERT DYNAMIC BITS HERE XXXXX > > ? > > Basically I think most people take the designs and turn them into XSLT. However this is usually done by hand as the design usually changes infrequently. > > Perhaps use Cocoon + Velocity :-) ? > > Goodluck > > Alex > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
