There have been lots of discussions about templating systems in Cocoon lately.
It started with the need to refactor the JXTemplateGenerator (which works well, thanks, but the code could be better structured for maintainability), and quickly branched out to “how about a new and improved templating system”.
You often learn a lot in such collective discussions with the brilliant people who are around cocoon-dev. Me, I’ve learned/realized three important things:
Attribute-based template languages (like Zope’s TAL, thanks Chregu for the link), are much more tool-friendly (read Dreamweaver-friendly) than tag-based syntaxes, like our current JXTG.
The main reason is that attributes quickly become “invisible” to the page designer, yet they move with the elements when cut and pasted or duplicated. And there are several such syntaxes around, so designers are getting used to working with them.
See my Alice and Bob story for details, there has been some argument but mostly agreement, assuming it’s doable. I think it is.
XSLT won’t go away for sure, its power is really useful when you need it, but for simple things it is simply too costly to learn. We need something better, there are some alternatives in Cocoon today but none is really satisfactory.
There’s some additional information, summaries and mailing list references on the Cocoon wiki.
We live in exciting times – an experimental “template” block was added recently to the Cocoon trunk, and several people seem to be available to work on this, so it might become a reality rather sooner than later. Stay tuned.