On 6/19/06, Rinku <[EMAIL PROTECTED]> wrote:

Hi,

Some sites:
[A]  http://java.sun.com/javase/

[B]  http://ant.apache.org/

Some notes:

1) L.H.S nav categories are concise. For example, "Reference" in [A]
above has links to all documentation resources. "Community" has all the
stuff about forums, issues etc etc (can map to JIRA, mailing lists, irc)


To me, having a Reference section, and a Download section on the LHS are
most important (I wouldn't mind losing "Quick Links"). If a "Feature
Summary" is required, perhaps it should be on the main page. A lot of the
"Project Documentation" section could probably be altered, perhaps only CI,
Team information, and licenses. Issue Tracking and Mailing Lists probably
shouldn't be nested if you want people to use them.

2) I like Brett's idea on trails, +1. See below for another tail
example; these are nicely categorised based on user's level of
experience and also what they intend to do.
http://java.sun.com/docs/books/tutorial/index.html


I absolutely love this.

3) I like the idea of minimal clicks to the dowload pages for binary and
sources , see [B]. Current Maven site is fine for binary download but I
don't see any downloads for sources?


Or IMO more useful, a repository link on the download page.

Also, is there a way to track the Frequently Viewed Pages (FVP), the nav
structure could be re-factored if any FVP are nested 'too' deep! But
that will be something to monitor over time :-)

The above are by no means definitive, just indicative. I am sure there
are lots of other (and may be better) examples out there.

cheers,
Rahul


I've been using the M2 homepage for almost a year now, and I still find
myself hiccupping on navigation. These tend to be the major items my Maven
usage revolves around:

Download
 *Maven 2.0.4 (contains source code/svn and installation instructions)
 *Maven Ant 2.0.4 (contains source code/svn and installation instructions)
 *Maven Embedder 2.0.4 (contains source code/svn and installation
instructions)
 *Tools
   **Eclipse
   **Netbeans

Documentation
 *Trails (I also love this idea, these can contain the mini-guides, and
Getting Started)
 *Books and Articles
 *FAQ
 *Wiki

Plugins Reference
 *Core
 *Mojo
 *External
 *Search

Community
 *Bug Tracking
 *Mailing Lists

Project Information
 *License
 *Team
 *CI

Thanks;
Eric

Reply via email to