Togo looks interesting Matt (and cheers Cliff). I've had to build a lot of CMS' and similar systems, and I've had to *thoroughly* think through the problems of whether to homebake one or use an existing one, etc. (if anyone is interested in this topic let me know). My goal for Inkling is that it offers a DSL to implement your own knowledge management system (not necessarily a CMS).
One of the features I wanted to support was multiple ORMS *and* persistence mechanisms (rdbms, couchdb, etc.) via ActiveModel, but have been working on a postgresql via ActiveRecord, mainly implementation of a CMS for a client. So Matt, if you ever wanted to discuss pooling efforts, etc., that'd be great. One of the key elements about inkling is that you can add 'acts_as_inkling' to any model and it's adopted by the system (given easy routing, access to work flows, etc.). It's also an engine and is meant to be cooperate with other engines (one of the classic problems of CMS' is that they are hard to integrate with shopping cart libs, etc. - each want a table named 'User', etc..). Inkling is a little unprepared for the public eye right now. I'll be updating the docs and polishing a few things after Nov 30th. Cheers, Nick On Nov 19, 12:36 pm, Clifford Heath <[email protected]> wrote: > On 19/11/2010, at 12:27 PM, Brian Troutwine wrote: > > > > > > > On Thu, Nov 18, 2010 at 8:16 PM, Matt King <[email protected]> wrote: > >> Hi all, > >> I hope it's not out of line to let you guys know about a project > >> I'm working > >> on. Togo is a CMS framework with a goal of integrating with all the > >> major > >> Ruby ORMs. DataMapper is my favorite ORM, so it's currently the > >> only one > >> supported (I'm planning on ActiveRecord next). > >> The CMS has list, search, filter, add/edit/delete functionality all > >> baked > >> in. All you have to do is include the Togo in your model to be able > >> to > >> manage the content in the CMS. It runs as a separate rack > >> application that's > >> independent of any framework you might be using, which is > >> intentional to > >> de-couple what you might use on your frontend from managing content. > >> I was hoping I could get some feedback from anyone here on anything > >> from > >> installation, compatability problems, feature requests, bugs, etc. > >> I'm > >> assuming if you're on this list, you're a DataMapper fan and use it > >> often, > >> and I'm building this for people like you (and me). I'm tired of > >> re-inventing the CMS for every project I work on. My aspiration is > >> to have > >> this become something similar to Django in the Python world. > >>https://github.com/mattking17/Togo > > >> and > >> gem install togo > >> I'm also looking for collaborators, if you're interested drop me a > >> note. > > > I'm interested and, to be frank, I'm often lazy. Could you make a > > demo-app that I can clone and interact with? > > If you're interested in content management frameworks, take a look also > at the excellent Inkling,http://github.com/biv/inkling, by a friend > of mine. > It's all nice and shiny with Rails 3 engines and everything. For > ActiveRecord, > however. Not sure if the author is considering DataMapper at present. > > Clifford Heath, Data Constellation,http://dataconstellation.com > Agile Information Management and Design -- You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en.
