Oh sorry - the reason I asked was that I didn't see a link to a repository in my initial poke around the site. I guess my lack of sleep is showing since I obviously didn't look or think very hard.
M. Gaspard Bucher wrote: > On Thu, Jan 8, 2009 at 6:11 AM, MarkMT <[email protected]> wrote: > > > > Is it open source? > > Yes of course ! MIT licenced. > > Maybe I need to present zena in a few words: > > The CMS started as an inside tool to help with my art projects and > associations. What I needed was a tool that was very flexible in the > layout / workflow / content but at the same time was easy to use to > post new content. If it's not easy, the content on the website just > ... rots. I also needed a strong multilingual support. I also > implemented multi-site support (mainly to ease on resources). > > Actually zena is used to build applications (training management, > project management) or websites (http://zenadmin.org, > http://rubyk.org, etc) or both at the same time. The main power of > zena is it's data model and the templating language. The model lets > you create new classes from the web with class inheritance so that > your site actually works with things that make sense to the domain you > are working in (Concerts, Albums, Tours, Songs, Houses, Friends, ...). > > Simple example of a template to display the concerts of a tour with > date and link to map: > > <ul do='concerts'> > <li do='each'><!-- in a concert context --> > <p class='date' do='show' date='event_at' tformat='concert'/> <!-- > display date with translated format 'concert' (defined in a yaml > dictionary) --> > <p class='title' do='[v_title]'/> <!-- display version title --> > <p class='map' do='location'> <!-- use a relation to move to > "location" context --> > <a do='[v_title]' set_href='[d_map]'/> <!-- dynamic attribute with map > --> > </p> > </li> > </ul> > > > > > > > > On Jan 7, 11:03 pm, "Gaspard Bucher" <[email protected]> wrote: > >> Hi there ! > >> > >> I want to port zena (http://zenadmin.org) from Rails 1.2.3 to Merb. > >> > >> There are 2+1 goals in this migration: > >> > >> 1. remove most hacks in zena that were needed in Rails > >> 2. improve modularity (choice of authentication, etc) > >> 3. (eventually improve overall performance, scalability) > >> > >> The two points do not have to be done at the same time. > >> > >> This is a pretty big change and I do not feel like doing it alone > >> (especially since I'm a merb newbie). > >> > >> Is there anyone who would like to help me with this ? > >> > >> Gaspard > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
