I am strongly in favour of moving the current wiki content to cwiki.
I'm very happy with it for other projects, and we already have it set
up to generate static sites in the Maven site template.
My general opinion about using the wiki for the site is that I prefer
to use it more for user contributed, "cookbook" style while sticking
to the Maven documentation for release-bundled, versioned
documentation. However, I'm happy for the people doing the work to
decide on the best way to use it :)
Cheers,
Brett
On 05/06/2008, at 9:20 PM, Arnaud HERITIER wrote:
Hi all,
Some Apache projects are now writing their documentations on
confluence @
Apache.
For example Apache Directory :
http://directory.apache.org/
http://cwiki.apache.org/confluence/display/DIRxSITE/Index
Even if Sonatype's book is helping a lot about Maven's
documentation, our
users are always complaining about it.
We have always the problem with maven web sites to split user's
documentation, projects reports.
Actually we extracted users documentations in external projects but
it's
not done for example for plugins and we have often some plugins
websites
with the documentation of the latest SNAPSHOT because we updated the
user
guide.
Couldn't we move our users documentations (core & plugins) in
confleunce
and keep maven generated sites (one per version) for technical
reference
guide ?
WDYT ?
Arnaud
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
