On 12/1/2010 20:46, Jörn Kottmann wrote:
To use the new CMS we have to request it from the Infrastructure
team like the stanbol people did:
https://issues.apache.org/jira/browse/INFRA-3199
Should we try the new CMS?
+1 for the CMS. I'm not a great fan of markdown, but
it beats both html and anakia IMHO. However, I have
no strong opinion...
--Thilo
Any opinions?
For me it seems that the new CMS is now the new conventional way of
managing website at Apache and its easy to do, so +1 for me to
go this way.
Jörn
On 12/1/10 7:08 PM, Jörn Kottmann wrote:
Here is a link with background information about the new CMS:
http://journal.paul.querna.org/articles/2010/10/22/evolution-of-apaches-websites/
The suggest way to use the CMS is to write the content in Markdown.
Here is a link to the stanbol project site in svn:
http://svn.apache.org/repos/asf/incubator/stanbol/site/trunk/
The layout must be as described here:
http://www.staging.apache.org/dev/cms.html#layout
Jörn
On 12/1/10 4:30 PM, Benson Margulies wrote:
Please consider using the new Apache CMS system for most of the
content. Feel free to use the maven site plugin if you like to
generate reports and such. My personal experience is that using maven
site as the primary mechanism for an entire project is a road to pain.
On Wed, Dec 1, 2010 at 9:59 AM, Jörn Kottmann<[email protected]> wrote:
Hello,
we have to create a new project website.
The current one is just a bunch of html files,
which had been pushed with maven to the sourceforge
web space after an update.
The mentor guide says
"It is recommended that an initial site is uploaded as soon as
possible".
Should we just stay with html, or use one of the
popular choices over at Apache:
- Apache Maven
- Apache Velocity Anakia
- XSLT
Over at UIMA we use Anakia, should we use
it here as well, any opinions ?
Jörn
