There are two things that the maven site documentation should accomplish
1. Top level view: what were they thinking when maven was designed
- What use cases does it attempt to solve, (with only core
plugins)
- What are the standards followed
- What maven does not try to solve.
2. Procedural view: HowTo with decision tree
- Should be split up by types of things to do. e.g. Copying files
- if j2ee, follow the standards set by war/ear plugin (with a link to the
detailed doc of that plugin) , if ( )....etc.
- Should include documentation of missing features also, so
everyone doesn't try and try to do something with maven that can't
currently be done, or that should be done another way in order to follow
the standards.
The poor mans solution to (2) is the FAQ - but I think the structured
approach adds a lot of value.
My reasoning for the above is that, as I see it, there are 2 kinds of
people - those that think procedurally - "how do I?", and those that
like/need to understand the theory behind how things work.
(apologies if this is already addressed - I haven't had time to read the
entire thread)
/Michael
