Peter D Bethke wrote in post #1141605: > Hello all, > > > I’m moving to Rails from another OO language where I’ve built my own > extensive CMS systems - and I’m the kind of guy who learns by breaking > things and figuring out why they broke. Strange method but true - I > guess > I’m just the impatient sort :) > > Since I’m most familiar with CMS architecture and multi-level > user/group/authenicated access systems I thought it logical to start > with a > Rails CMS app to see how its put together there. Naturally I’m at a loss > where to start because there seem to be a lot of them. > > Initially I was interested in BrowserCMS because of its in-page editing > (neat) and group-based access model, but although it says its Rails 4 > compatible, when I load the gem it downloads a whole slew of Rails 3.2 > gems > to support it - leading me to believe its not truly Rails 4 ready. Maybe > I’m mistaken. > > Now I’m considering Comfortable Mexican Sofa because its really seems to > be > actively developed and does seem to function as a plug-in instead of a > self-enclosed system (leaving me more to mess around with), though it > seems > to lack a robust user system (though from what I have read “there’s a > gem > for that”). > > I’ve looked at Refinery (seems really out of date) and locomotive and a > few > others. Comfy seems the only one that is making an effort to stay up > with > the latest rails. I may be wrong - just an initial impression. > > Any thoughts? Just looking for an impartial recommendation for an > “experienced newbie” as it were. > > > Best, > > Peter Bethke
I think you're approaching this question the wrong way. The CMS is not for you, it is for your content managers. In my opinion, to properly choose a CMS you must ask these questions: What type of content will be hosted by our CMS? How dynamic is the content? What type of people will be managing this content? Ruby is great, and because of our love of Ruby we may be inclined to go with a Ruby based CMS, but none of the Ruby ecosystem solutions are that great from a content management perspective. There are other ecosystems that I feel are more mature when it comes to content management. Case and point is wordpress. I hate everything about its backend. After doing any kind of development with it i feel like i have to take a shower. But it's fantastic from a UI point of view. You can get a full site up and running in days. There is practically zero learning curve for users. In regards to the question of "How dynamic is the content?", what i mean by that is that CMS by their definition, like static content. A user types a bunch of stuff, and that stuff is served in different places. If on the other hand you have a lot of dynamic relationships, covered by complex business rules, then a homegrown solution might be your best bet. If you find yourself constantly coding new things, and looking for ways to circumvent default CMS functionality, then you've made a bad choice. Other than that, I also vote for Browser CMS. It is a solid, well built CMS, with a very good google group. Don't worry too much about the Rails 4 stuff. P.S. Also pay attention to data stores for these. Some are SQL some are NoSQL. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/c97da2fdd95e3eac3a8a10b809be8b09%40ruby-forum.com. For more options, visit https://groups.google.com/d/optout.
