Cocoon Day 2003

Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 15014 invoked from network); 3 Oct 2003 16:30:06 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 3 Oct 2003 16:30:06 -0000 Received: (qmail 98810 invoked by uid 500); 3 Oct 2003 16:29:49 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 98773 invoked by uid 500); 3 Oct 2003 16:29:49 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 98752 invoked from network); 3 Oct 2003 16:29:49 -0000 Received: from unknown (HELO email06.aon.at) (195.3.96.75) by daedalus.apache.org with SMTP; 3 Oct 2003 16:29:49 -0000 Received: (qmail 240920 invoked from network); 3 Oct 2003 16:29:51 -0000 Received: from n620p002.dipool.highway.telekom.at (HELO gmx.at) ([212.183.87.98]) (envelope-sender ) by qmail6rs.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 3 Oct 2003 16:29:51 -0000 Message-ID: <3F7DA3FE.6020605@gmx.at> Date: Fri, 03 Oct 2003 18:29:50 +0200 From: Alexander Schatten User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 X-Accept-Language: de-at, en-gb, en-us, en MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Re: html templates - best practise References: <002f01c3898f$acb1fbe0$1916a8c0@cweb1> In-Reply-To: <002f01c3898f$acb1fbe0$1916a8c0@cweb1> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I developed a way of "callback" templates. Look at this: (0) consider a HTML design like this: +--------------------------------------------+ | Page Title (each page different) | +--------------------------------------------+ | Main Navigation (for all pages the same | +--------------------------------------------+ | | | | | Content (each page different) | | | | | | | +--------------------------------------------+ | Footer (each page different) | +--------------------------------------------+ (1) first of all there is the default.xsl stylesheet it looks (very reduced version) like this: Cocoon Day 2003

oder

(2) then there are the specific stylesheets for different parts of the website, looking like this: Titel the include includes the default stylesheet, in which the root template it the first to be executed. then, this root template builds the HTML "frame" and calls the named templates to fill in the concrete content. The main advantage is this: in the default.xsl stylesheet inside the root template is xhtml that can be edited with any editor e.g. dreamweaver. the only xsl tags are the 2 or 3 call-templates and those are usually ignored by html editors like dreamweaver. I use this in many projects and it works excellent also offline (with normal XSLT transformation e.g. using ANT). alex --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org