- apply the maven site skin consistently (
- site structuring (this already had concrete proposals):
- see also Better Builds with Maven section on "separating developer and user content"
- set up a staging site
- remove "2" from Maven 2 references (it's just Maven). We'll still refer to Maven 1.x in comparisons and pointing to the Maven 1.1 docs.
- create a plugin link page that is categorised (j2ee, ide, artifact handling, test, packaging, CI, archetypes, source generators, reports) - to be automated later by additional metadata
- enhance plugin link page (more plugins, add current release version and quality (dev, alpha, beta, stable) - to be automated later (
- add search box to the index page (google for now)
- chop up the getting started guide so it is again something you could do in 10 minutes to get a feel for Maven (perhaps go back to the level of the original guide). Maybe rename to something else? I used to call it "the 10 minute test" on Maven 1.
- categorise the guides page, rename the page as "Index" (not index.html) -
- relabel "other projects FAQ" as "guide for sync partners" or similar. It should go into a repository related subsection.