Hi Kiran, thanks for your answer.
Our event takes place in october, but we have to put some content on the web this week. (BTW: here's the current web site for the event:
http://openworldforum.org/ ) and I only have a limited amount of time to work on it (say, a couple of days).
If I had the time, I would have tried the following approach: use a content repository with a model similar to the JCR (
http://en.wikipedia.org/wiki/Content_repository_API_for_Java), put a REST API on top of it, and use a rich client JS application as the management interface (for instance, based on AngularJS). I already have a prototype implementation for a repository, and I guess Nodular is also a promising candidate, adding a REST API (such as this one:
https://docs.jboss.org/author/display/MODE/REST+Service+3.x - which is actually closely related to the JCR API) on top of it should be trivial to implement, but developing the management UI in Angular or any other JS framework is much more work than I can dedicate to this project in the short term. This is in accordance with the architecture described by my friend Henri Bergius (of Midgard fame) here:
http://bergie.iki.fi/blog/decoupling_content_management/
However, given the limited amount of time and resources I have right now, my new plan is currently to use an existing CMS for the back-office (I'm leaning towards FeinCMS, a light-weight Django-based CMS) and custom Flask code for the public front-end to get a website quickly running, and maybe work on something more elaborate during the summer.
S.