If I may, I would like to ask another question. Why a Rails CMS? Shouldn't the question be; whats the best CMS? If I needed a CMS, I wouldn't limit myself to

If I may, I would like to ask another question. Why a Rails CMS? Shouldn't the question be; whats the best CMS? If I needed a CMS, I wouldn't limit myself to something built on Rails. Sure, you may need to extend that CMS and you want not want to do anything in PHP, but you should be able to do small modifications easy enough. If you need anything big modifications, then perhaps you would be better off building something from scratch. Also consider the goals of a CMS vs your own goals as a developer. A CMS needs to be flexible for non developers to handle a wide range of tasks. Your own system only needs to handle the basics but be easily extendable (something which Rails should largely bring by itself.) In other words, Rails is already a very basic CMS. Otherwise, I can't answer the question of "what's the best CMS" in general because different systems are better for different needs. I imagine the Ruby / Rails options are the same. You would likely be better off trying each of those that catch your eye and making a decision from there.