#acl andybuckley:read,write,delete,revert All:read #pragma comment-owner andybuckley #pragma page-filename DEV/versions/163936 Lazily copied from my email to the list for reference <<BR>> Can I request that if the templates are being re-written some attention should <<BR>> be paid to the idea of making Mailman embeddable within a parent site's HTML<<BR>> framework and styles. For example, I run a system called !HepForge where several<<BR>> types of web technology are hidden behind Apache and the page headers and<<BR>> footers, including CSS imports, are added by Apache output filters. A<<BR>> significant amount of work is required to edit Trac and Mailman templates to<<BR>> make them work with this sort of system - see<<BR>> [[http://trac.edgewall.org/ticket/4264|http://trac.edgewall.org/ticket/4264]] for a bit more detail on the issues with Trac. In particular, it would be really nice if * the bits of the template which define <head>, <body> etc. are defined in one<<BR>> pair of header and footer files, so they can be turned off easily. * the proposed Mailman CSS files "namespace" everything by placing all Mailman<<BR>> content within a div, e.g. <div id="mailman">...</div> and then prefix all CSS<<BR>> rules with "#mailman" - this stops the Mailman styles from leaking out into the<<BR>> parent page elements. Sorry to dwell on implementation specifics at this stage, but it's an issue<<BR>> that's often ignored but is actually pretty important. I can add this to the<<BR>> wiki if it's relevant?<<BR>> Genshi has been mentioned a few times. My impression was that it insists on<<BR>> producing valid XML output, which is nice, but doesn't necessarily play well<<BR>> with ideas like factorisable head/foot portions. Also, can it be used for<<BR>> templating the automated email messages, i.e. plain text? I'm not speaking from<<BR>> exceptional familiarity with Genshi here, but these suspicions made me use<<BR>> Cheetah in place of Genshi for one of our projects... can anyone confirm/refute?