commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dirk Verbeeck <>
Subject Re: [all] Which website entity?
Date Tue, 02 Mar 2004 20:20:02 GMT
As long as the result is the same I don't really care much about 
exactly how it is done, I'll going to experiment with the 
commons-site.jsl solution more this weekend.

-- Dirk

Mark R. Diggory wrote:
> As a plausable solution, rebuilding the 
> commons-build/xdocs/navigation.xml and commons-build/navi_incl.xml 
> document to draw its contents from the menu "ent" files. Set the types 
> of the "about menu" to "header" and the rest to "footer". These 
> attributes are used in the commons-site.jsl to separate the rendering of 
> the navigation menus as so:
> <jsl:applyTemplates select="$nav/body/menu[@type='header']"/>
> <jsl:applyTemplates select="$nav/body/menu[not(@type)] | 
> $nav/body/search"/>
> <jsl:applyTemplates select="$projectNav/body/menu"/>
> <jsl:applyTemplates select="$nav/body/menu[@type='footer']"/>
> This means that any menu of type "header" comes before "no type" or 
> search, which comes before the type footer.
> This means that it doesn't matter the order for which they are added to 
> the navigation.xml as entities and they can even be added to the 
> navigation.xml as one entity and still show up either above or below the 
> various project navigation and menu items added by the project.
> -Mark

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message