This is a genuine problem, but it's not just for Ruby on Rails. Every framework in every language has this problem. It's just that the ease of developing the "c

This is a genuine problem, but it's not just for Ruby on Rails. Every framework in every language has this problem. It's just that the ease of developing the "custom app" portion of the site in RoR throws the wasteful yak-shaving wheel-reinvention of writing a CMS in sharper relief, IMO. Trying to find a generalised "CMS API" is a nice idea but honestly I wonder if it's even possible. Maybe it's just at too high a level to standardise. I can't even think of a good CMS, let alone some paradigm I'd want as the "standard" .. Got to agree with him on one point though - stay away from things like RadiantCMS, they're a trap. You think they will save you time, but they will not. These days if I had to write a small business site I'd just write some basic editing pages on the back end and who cares how it looks - the clients sure don't.