accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: wiki & release
Date Wed, 26 Oct 2011 20:14:56 GMT


As you are researching web-site and documentation technologies, I'd like to recommend an
approach that we (Karaf) have found useful: 

    • Consider creating a "site" project in your SVN tree to hold all of your website stuff.
This will allow to you tag it corresponding to each of your product releases. 
    • Take a look at Scalate Wikitext. We use this on Karaf to write our HTML documents,
and it uses a very easy wiki-like syntax.  In fact, we use it for our site and for our
documentation.  We also use PrinceXML to generate PDF's from the documentation stored in
our source-tree. 

If you would like help, feel free to ask! 

Mike Van 

ASF - Committer 

----- Original Message -----

From: "Billie J Rinaldi" <> 
Sent: Wednesday, October 26, 2011 4:00:00 PM 
Subject: Re: wiki & release 

On Wednesday, October 26, 2011 3:15:16 PM, "Jesse McConnell" <>
> Just a friendly note that in jetty we have started to look at 
> abandoning using the wiki in favor of a docbook approach to produce 
> documentation. Also it looks like the apache directory folks are 
> going a similar route of producing their wiki documentation through 
> docbook as well. Much of the maven documentation has trended the same 
> way, at least that produced by Sonatype. If your starting from 
> scratch it may be worth taking a few minutes to investigate other 
> options. There are also other options like markdown and some tooling 
> that lets you go from wiki text files into docbook and then be 
> transformed into xhtml, pdf, eclipse-help, and many other options all 
> in a maven build. 

We are already using markdown for our main web site, although it isn't being built with maven.
 We could attempt to use the main site in place of a wiki once CMS is enabled for it.  The
downside is that only committers would be able to edit it.  It would be nice if others could
contribute as well. 


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message