comparison of CMS for Ruby On Rails

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    2 Favorites

    comparison of CMS for Ruby On Rails - Presentation Transcript

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

    + Thomas R. KollThomas R. Koll, 2 years ago

    custom

    1847 views, 2 favs, 0 embeds more stats

    A short comparison of content management system ava more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 1847
      • 1847 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 2
    • Downloads 40
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories