Hi, On Mon, Aug 25, 2014 at 2:23 PM, Radu Cotescu <[email protected]> wrote: > ...I've started working on a website prototype using Jekyll at [0]. The reason > for this is that the Apache CMS didn't seem very flexible when it came to > creating new templates (Perl is really not my cup of tea)....
IIUC the usage scenario is that people have to install something (your vagrant box?) to generate the website pages, commit those to svn and let svnpubsub sync the live site. I'll just note that requiring people to install *anything* just to edit the project's website is likely to lower the number of website contributions. The beauty of the Apache CMS is that you can just edit content in svn using any tool, and use https://cms.apache.org/ to check staged versions and make them live. AFAIK it is possible to integrate non-Perl build systems into it, but I haven't done that myself. > ...I think the effort should now be channeled towards creating a more adequate > website in order to graduate and set-back on the next releases for a while... IMO the current website is not a blocker for graduation. -Bertrand (don't get me wrong: it's great to see work on the website!)
