Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

comparison of CMS for Ruby On Rails

3,625 views

Published on

A short comparison of content management system available for ruby on rails

Published in: Technology
  • Be the first to comment

comparison of CMS for Ruby On Rails

  1. 1. <ul><ul><li>content management systems </li></ul></ul><ul><ul><li>for </li></ul></ul><ul><ul><li>Ruby on Rails </li></ul></ul>Thomas R. „TomK32“ Koll http://ananasblau.com
  2. 2. the usual tasks <ul><li>application </li></ul><ul><li>many controllers </li></ul><ul><li>many models </li></ul><ul><li>users and groups </li></ul><ul><li>complicate layouts </li></ul><ul><li>my mom's website </li></ul><ul><li>much content </li></ul><ul><li>many images </li></ul><ul><li>editable </li></ul><ul><li>a map controller </li></ul><ul><li>maybe multilingual </li></ul>
  3. 3. just basics: comatose <ul><li>provides only pages, no login, user, menu </li></ul><ul><li>reuses other plugins (acts_as_versioned, acts_as_tree) </li></ul><ul><li>doesn't inherit its Controller from ApplicationController (helpers and such missing). You can, but don't forget to activate class cache </li></ul>
  4. 4. roxanne <ul><li>very very basic like comatose but with users </li></ul><ul><li>basically a in-place-editor with a lot of JS </li></ul><ul><li>comatose is better documented and tested </li></ul>
  5. 5. the weird: geego <ul><li>installation could be more comfortable </li></ul><ul><li>no default templates or initial pages (we learn by examples) </li></ul><ul><li>uses ftp to publish, might not be your workflow (a rake task would be better) </li></ul><ul><li>no view before publishing </li></ul>
  6. 6. .jp on js: rubricks <ul><li>almost only japanese docs </li></ul><ul><li>Javascript everywhere </li></ul><ul><li>like phpnuke </li></ul><ul><li>very very spare basic system and components </li></ul><ul><li>component based </li></ul>
  7. 7. ScriboCMS <ul><li>looks pretty complete for a blogging engine </li></ul><ul><li>absolutely no website, docs or similar </li></ul><ul><li>dead (last release january 07) </li></ul>
  8. 8. <ul><ul><li>it's not dead: mephisto </li></ul></ul><ul><li>best is integration as plugin. Split up into an admin controller, a front controller and drops and don't forget to post an article... </li></ul><ul><li>views/layouts editable through admin interface </li></ul><ul><li>only two types of sections (yes, it's binary) </li></ul><ul><li>template system: liquid </li></ul><ul><li>many plugins </li></ul>
  9. 9. <ul><ul><li>radiant </li></ul></ul><ul><li>has it's own layouts/synatx </li></ul><ul><li>two plugins for integrating your rails app </li></ul><ul><li>many plugins available </li></ul><ul><li>available as a gem </li></ul><ul><li>has it's own template engine: radius </li></ul>
  10. 10. goldberg <ul><li>excellent group rights management (inheritance) </li></ul><ul><li>rights management per controller and action (be careful!) </li></ul><ul><li>easy integration of you own controllers </li></ul><ul><li>no extra layout for admin interface by default </li></ul><ul><li>no proper 404 </li></ul>
  11. 11. the ideal CMS? <ul><li>inheritable group-rights </li></ul><ul><li>routes administration (but with export) </li></ul><ul><li>completely separate admin interface </li></ul><ul><li>migrations independent from the app </li></ul><ul><li>views/layouts editable (but again with export) </li></ul><ul><li>any other wishes? </li></ul>
  12. 12. appendix <ul><li>download at: http://ananasblau.com/cms-for-ruby-on-rails </li></ul><ul><li>author: Thomas R. “TomK32” Koll </li></ul><ul><li>license: creative commons by share-alike </li></ul><ul><li>last revision: 2007/12/10 </li></ul><ul><li>contact: [email_address] </li></ul>

×