Hi all,
I am noticing that the very long list of commons components and commons
sandbox components makes the left nav for the Maven enabled projects quite
difficult to read.. The key information about the component gets lost in
the Menu.
What do you think of using the collapse=true attribute or
hi eric
this has been discussed before and the consensus was that the
collapsable menus would be the best solution. the issue is that some
maven work is needed to make them work. (just setting them to
collapsable does nothing useful since the collapsable feature is
designed to work with maven
the seperate pages.
And maybe at this point update the commons main site to be just Maven lF?
Eric
-Original Message-
From: robert burrell donkin
[mailto:[EMAIL PROTECTED]
Sent: Sunday, February 15, 2004 2:35 PM
To: Jakarta Commons Developers List
Subject: Re: Change Commons Nav
On 15 Feb 2004, at 14:33, Eric Pugh wrote:
snip
And maybe at this point update the commons main site to be just Maven
lF?
we're still a little way off being able to think about doing this. we
need all the components sites switching to the mavenized documentation
build first. we need
On 15 Feb 2004, at 14:33, Eric Pugh wrote:
snip
Something that might work well at least in the short term is to ditch
all
the items under each menu item, and instead have the menu just link to
a
page on the main http://jakarta.apache.org/commons/ site. That would
reduce it down to 8
I've been a little aggressive this morning in terms of cleaning up the
maven xdoc and build files. Be warned I removed
/jakarta-commons/xdocs
/jakarta-commons/maven.xml
/jakarta-commons/project.xml
/jakarta-commons/incl_nav.xml
/jakarta-commons/navigation.xml
/jakarta-commons/project.properties
I'm -0 to hiding the commons proper links. I think that they are a key part
of letting us and users navigate around the commons site, and are part of
keeping it one community. Also, the maven collapsable stuff is slow and
clunky and I basically hate it. (the sandbox is different for other reasons)
