And I have to say I very much like being able to edit the main site using the webui. See https://blogs.apache.org/infra/entry/the_asf_cms
Ralph On Jun 6, 2012, at 5:36 PM, Ralph Goers wrote: > > http://loggingtest.staging.apache.org/index.html is up. > > Ralph > > > > On Jun 1, 2012, at 5:42 AM, Ivan Habunek wrote: > >> Joe Schaefer suggested on JIRA [1] to have the site contents in pure >> Textile markup instead of Django templates as it is now. The benefit >> of this is that it would be somewhat simpler to write contents (no >> need for the template boilerplate). >> >> Personally I'm somewhat inclined to leave it as it is now since it's >> more flexible and the boilerplate is really not that bad. >> >> The current contents are located at [2]. >> I will eventually change the ".twig" extension to something else since >> we're not using Twig any more. >> >> To illustrate the point further, some projects, like Esme [3], have >> something similar, but with Markdown instead of Textile. >> >> What do you think? >> >> Regards, >> Ivan >> >> [1] http://s.apache.org/HGr >> [2] http://svn.apache.org/repos/asf/logging/site/branches/cms/trunk/content/ >> [3] http://svn.apache.org/repos/asf/esme/site/trunk/content/ >> >> On 31 May 2012 13:44, Ivan Habunek <[email protected]> wrote: >>> On 31 May 2012 12:23, Ralph Goers <[email protected]> wrote: >>>> My understanding is if you want to use their system we can use their web >>>> UI to edit stuff and we don't really have to do anything. >>> >>> We have to at least adapt view.pm and path.pm, like Joe Schaefer said. >>> By default they are configured to process only *.mdtext files. I'm >>> working on it. >>> >>>> Whatever you do, you can just use the area I already created which is >>>> documented in the Jira issue. >>> >>> OK, I will use the /site/branches/cms/trunk/ folder. >>> >>> Regards, >>> Ivan >
