[maven-bug] Created: (MAVEN-276) Use a single navigation.xml for a site

[bo...@werken.com]

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-276


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-276
    Summary: Use a single navigation.xml for a site
       Type: New Feature

     Status: Assigned
   Priority: Major

 Time Spent: Unknown
   Estimate: 3 hours

    Project: maven
  Component: None

   Assignee: Jason van Zyl
   Reporter: Ben Walding

    Created: Sun, 16 Feb 2003 6:06 PM
    Updated: Sun, 16 Feb 2003 6:06 PM

Description:
I'm thinking of making a change to site navigation. This change will be fully backward compatible.

The general aim is to remove the requirement to have different navigation.xml files scattered over your site. You'd simply generate a single navigation.xml that contained all levels in the one file and then site.jsl would generate the appropriate navigation on each page depending on the context of your location.

Essentially the change would allow a better level of navigation and provide more feedback to the user at to where you are within the site.

If you click on a "menu" on the side bar, it would expand to show content within that menu. This would be achieved using xpath to work out whether the node should be expanded or not. There should be no requirement for java code.

Menus / Items will be allowed to collapse by setting attribute collapse=true

Menus / Items may have icons denoting the expanded / unexpanded nature of the node.

If a node is set to collapse=true, it will be collapsed unless it is selected. Children inherit expansion state of parent.

Initially pages will require a <location> entry in the properties section of the xdoc file. This requirement will be relaxed as soon as a reliable way of identifying page location is created. (This may not be necessary by the time I finish in any event).
Navigation Selection

The navigation file that is chosen will be determined by searching back up the path for the closest navigation file. In the case of generated docs, they will trace back up the normal doc navigation tree. I think this is what happens at the moment, but I'm not 100% sure.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.werken.com/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira