Hi,
maven site uses a quite simple syntax known as APT ("Almost Plain Text")
[1], simpler but less powerful than MarkDown. For the moment we didn't
have time to play so much with in in LMF, only for the welcome page of
the site [2]. So still not sure what is the right option... specially
some important bugs generating more than one report, or at least we were
not able to properly configured (for instance to publish both javadoc
and rest api reports).
Anyway, as I reported in INFRA-5624 [3], the project URL still returns
404. But first they need to know [4] if we'll use CMS or svnpubsub-based
site. Not sure if we could change this in the future... but at least I'd
like to put something like "coming soon" there meanwhile we wait until
the other resources (git, jira and so on).
Cheers,
Sergio
[1] http://maven.apache.org/doxia/references/apt-format.html
[2]
https://code.google.com/p/lmf/source/browse/src/site/apt/index.apt?name=default
[3] http://issues.apache.org/jira/browse/INFRA-5624
[4] http://www.apache.org/dev/infra-contact#what-we-need-to-know
On 05/12/12 22:32, Andy Seaborne wrote:
The website has two distinct faces : inward to the project and it's
processes, and the maven plugins are good at doing this with reports,
but also outward to users for documentation and maven really does not do
much for that aspect in my experience.
In a separate site, there is some stuff that needs to be kept in step
with versions but, with careful writing, it's not very much.
The outward facing documentation, and I mean more than just javadoc,
often has a different lifecycle than the inward-looking project reports.
CMS is great for maintenance - read the website, see something to fix,
press "edit" and do it there and then in the browser. The bulk content
is markdown+tables.
It may be possible to combine - look at other projects and ask them if
they look interesting.
Jena uses CMS - we wanted a separate, designed information architecture,
one of the project members (Ian) was keen to do it that way and he did
the bulk of the work. It used HTML content converted to markdown.
Andy
A pro-maven link:
http://blog.akquinet.de/2012/04/12/maven-sites-reloaded/
--
Sergio Fernández
