Robert Burrell Donkin did the initial implementation of this menus.dtd
for the Betwixt site. (the current main site also uses it and the
sandbox components I mavenized as well)
I like the way you can put the About Us section above the
Commons DBCP without any special scripting.
Dirk Verbeeck wrote:
Robert Burrell Donkin did the initial implementation of this
menus.dtd for the Betwixt site. (the current main site also uses it
and the sandbox components I mavenized as well)
I like the way you can put the About Us section above the Commons
DBCP without any special
For example the View CVS and Download menus are usefull on the
main site but on the DBCP site they aren't. There you have a specific
downloads page:
IMO, the downloads page of a project is additional. This will become more
obvious when we get a different background colour for the project
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
As I started looking at updating some of the websites, I realised that we
have two competing approaches:
- incl_nav.xml
- menus.dtd
I have been updating everything to use the former, but I suspect others may
be updating towards the latter. Have we agreed on which to use? If so, can
we mark the
Heh. Looks like Dirk created/moved the menus.dtd the other day.
Any reason why we should be using menus.dtd Dirk?
Betwixt, Pool, Launcher and DBCP are using it.
Hen
On Sun, 29 Feb 2004, Stephen Colebourne wrote:
As I started looking at updating some of the websites, I realised that we
have
Yes, right now the direction we've been taking is to include the common
navigation using the following Entity Reference strategy:
?xml version=1.0 encoding=ISO-8859-1?
!DOCTYPE project [
!ENTITY commons-nav SYSTEM ../../commons-build/incl_nav.xml
]
project name=Math
titleMath/title
