Hi Tommaso and all, I'm not sure if our bsd jail would actually be powerful enough to server concurrent requests quickly enough, I haven't had enough time yet to play to see how to best set it up but the first attempts looked rather disappointing.
I think the obvious flaws of the current site are not a reason not to proceed iteratively. Having a prototype is good to know in which direction we want to go, now we should improve the actual site. I reckon the process for publishing the site offers room for improvement, I think this improvements will arise when we actually use it. In the process of using it we will also learn about Clerezza from the user perspective. We will create templates that we can use both on the site and on demo instances and that might also show as how we can best improve (CLEREZZA-147) the default css and renderlets. I very much appreciate the fact, that now others are caring about the site as well. I understand the wish to have the ideas of the prototype quickly, however I think that after half a year of little activity (8 revisions all by me) we must not fall into a blind activism. Our site shall be easy to maintain so that it allows up-to-date information. Compromises on the easiness of maintainability are only justifiable if they help us improve Clerezza (as it already did by showing bugs in the stable serializer). I think creating a style for Clerezza based on the design concepts in the prototype would be the best next step. If we can use components of the trialox CMS to make the editing easier (and closer to wysiwyg) that would be great as well, but I find it a bit strange that after half a year that nobody actually tried improving the site (concluding this from the lack of commits or posts/issues describing failures) we should conclude that the current process isn't practicable. If in another half a year we see that even after having repeatedly updated the site it still takes unbearable extra-time to perform an update then we should reconsider changing the process. Apache CMS might be an alternative, static html files hardly are. Reto On Thu, Mar 17, 2011 at 10:35 AM, Tommaso Teofili <[email protected] > wrote: > 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) > > > > > >
