On 15/06/2011 15:19, Rob Weir wrote:
On Tue, Jun 14, 2011 at 8:40 PM, Greg Stein<[email protected]>  wrote:

Anakia is "sooooo last decade" technology and has some requirements
for everybody that wants to use it (eg. java :-)

If the new CMS can be used, then I'd recommend going with that. It
would be nice to get the community working with that today, as it
should be a good tool to use in the long-term. (Anakia gets to be a
pain for larger sites)

The CMS is newer than that documentation, which may be why it "prefers"
anakia.

Please take a look, and I can help with any authz bits or other setup
(just lemme know what I need to do).

IOW, my +1 is for the CMS. If we find that the community doesn't like
it, then we can make another choice for the long-term site.


With the CMS, would we also need to check in the generated site into SVN?
Or do we deploy "live" from the CMS? I assume this is the later, which would
be a lot simpler.

The markdown is in subversion. You can edit it either offline and commit or you can use (a fairly basic) web UI. From the webUI you can publish the site, but there are also scripts to enable you to do it from the command line.

Can you point me to a project that uses this for their project's website,
something that I can look at and potentially use a boilerplate for our site?

I recently built the boilerplate for the Rave podling (which in turn was stolen from another podling, Clerrezza I think). If you checkout http://svn.apache.org/repos/asf/incubator/rave/site/trunk/ and look over the history you'll get an idea of how we built the site up for that podling. The first commit is a fairly bare bones template you could reuse with just a little find/replace.

Once you have this template in place you need to ask infrastructure (via a JIRA ticket) to turn on the site publishing features.

As an ASF committer you can check out the UI of some of the foundation wide sites, such as http://community.apache.org (you need the bookmarklet from the bottom of https://cms.apache.org/

Ross



--
[email protected]
@rgardler

Reply via email to