Maven Site Refinements
----------------------
Key: MNG-2467
URL: http://jira.codehaus.org/browse/MNG-2467
Project: Maven 2
Issue Type: Improvement
Components: Documentation: General
Reporter: Marvin King
- apply the maven site skin consistently (MNG-1212)
- site structuring (this already had concrete proposals):
* http://mail-archives.apache.org/mod_mbox/maven-dev/200602.mbox/[EMAIL
PROTECTED]
* http://mail-archives.apache.org/mod_mbox/maven-dev/200602.mbox/[EMAIL
PROTECTED]
* 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 (MNG-1213)
- 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) -
MNG-1540
- relabel "other projects FAQ" as "guide for sync partners" or similar. It
should go into a repository related subsection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
