On 7 Jul 2011, at 07:17, Jasha Joachimsthal wrote: > With RAVE-45 (Non localhost support) we have a feature that goes beyond > "unzip the binary distribution and run Tomcat". Such features need > documentation how to configure / extend / customize the default setup.
I think the main task users have with Rave is setting up their own custom sites with extensions and so on, so there is a clear need for documentation on this. (I'd like to know how I'm going to deploy Rave extensions too!) > Where should we document this? "The code is the documentation" or "have a > look at the test case" is not what users like. Should we place documentation > on the website or on a wiki? If it's going to be the website, how can we > maintain an increasing set of features to be documented without creating a > large menu on the left hand side (e.g. oAuth, custom databases, login > mechanisms, skinning)? > Any thoughts (from the mentors)? > > Jasha Joachimsthal > > Europe - Amsterdam - Oosteinde 11, 1017 WT Amsterdam - +31(0)20 522 4466 > US - Boston - 1 Broadway, Cambridge, MA 02142 - +1 877 414 4776 (toll free) > > www.onehippo.com
