addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcredit-cardcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobe--smallglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1launch-new-window--smalllight-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

what are the issues with current Ruby on Rails based CMS?

From: user 7.
Sent on: Wednesday, May 26, 2010 10:25 PM



Just a thought if some one wanted to build a whole new CMS using Ruby on Rails and not consider whats already available in Radiant / BrowserCMS / Adva CMS / Rubricks / super simple cms…etc., why would they want to do it? Can someone point out to the merits and demerits of the existing CMS systems in place?


Or if some one is looking out for a new CMS system what are they looking for?



Satish N Kota

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy