commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Colebourne <>
Subject Re: [all][site] Site menu proposal
Date Mon, 08 Mar 2004 13:31:59 GMT
First off, I'm very glad to actually have a website to
play with that has expandable sections for the
components. Up until now we have been guessing what it
would be like.

On home, the components really must be linked in the
left nav, visible from the start. They are commons.
Its also easy to forget with a fast connection that
expanding and collapsing a menu goes to the server. We
could consider having sandbox as collapsed however.

Similarly on the project page, we need to get all the
project docs at the top with a different
background/clear separator.

I could live with partially collapsed menus for
components here - components menu open if viewing a
component, sandbox menu open if viewing a sandbox


 --- Dirk Verbeeck <> wrote: >
Hi all
> I have made a mavenized commons site with an
> alternative menu 
> structure to the current proposal 
> (
> The page content has to be updated but I wanted to
> show the menu first.
> and as example I have also rendered the DBCP
> component site:
> As you can see the general pages and the component
> site have a very 
> similar menu structure. The common site has a
> download, CVS & related 
> top menus where the component site has a component
> specific top level 
> menu (including a specific download page) & Project
> Documentation.
> I collapsed the components & sandbox menus. If a
> direct link from the 
> homepage to each component is needed then I propose
> a table on the 
> page itself like on the jakarta homepage.
> Now you have to click on the components/sandbox menu
> item and then 
> select a component (2 clicks).

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

View raw message