Hi all, at first I thought the best solution was to eat our own dogfood, like Reto said, then I realized we have a dedicated zone for Clerezza which can be good to demonstrate its capabilities. So now I think the best idea is going on with Apache CMS to quickly deliver our website, and of course provide pointers to our Clerezza zone to let people "have a look" at Clerezza. By the way, I like Tsuy's prototype. Cheers, Tommaso
2011/3/17 Tsuyoshi Ito <[email protected]> > hi > > i think using apache clerezza to generate our website a good idea but > i also think in the ASF context this not possible without a lot of > overhead: > > currently the following steps have to be done > > 1. load content from the svn repo into a apache clerezza instance > (access or own instance needed) > > 2. edit content in a rudimentar html editor (not wysiwyg) > > 3. export content with a clerezza tool => generate html files etc. > > 4. rdf data and html files have to be updated in the svn repo. > > 5. page has to be published to apache.org server > > There is no real benefit having content as rdf right know - so I don't > see why we should do the extra steps. > > storing website content directly in svn repo seem to be easier to > maintain (step 1 & 3 are obsolete) > > cheers > tsuy > > On Wed, Mar 16, 2011 at 10:22 PM, Bertrand Delacretaz > <[email protected]> wrote: > > On Wed, Mar 16, 2011 at 10:03 PM, Reto Bachmann-Gmuer > > <[email protected]> wrote: > >> Currently in svn we store data from which the whole website can be > generated > >> (by using clerezza) but not the generated files. Should we add them to > SVN > >> as well?.. > > > > Yes, if the website content is available in svn that's fine. > > > > Svnpubsub [1] can the be setup by ASF infra for near-instant > > publishing of updates when they are committed to clerezza's svn. > > > > -Bertrand > > > > [1] > http://journal.paul.querna.org/articles/2010/10/22/evolution-of-apaches-websites/ > > (dunno if there are other docs) > > >
