Note
There is no comprehensive list of Rails Content Management Systems (in development or otherwise), so you’re going to have to use Google (or Yahoo, if that’s your thing).
Update: There’s a list of rails CMS apps at RailsBased.org – maybe a place to start your search
Rails Behind a CMS
What about using the CMS as a proxy? Create a custom Content Class for each of your Rails applications. Instances of that Class act as proxies and fetch data from the Rails application, depending on how different your Rails applications are, it may also be possible to get by with only one custom Content Class and each instance just holds the URL to the Rails app and any other relevant integration data. In this model, Rails is behind the firewall, so Rails only needs to do authorization as authentication can be trusted, or you could also do authorization in the CMS and have your Rails app be auth/auth free. You could either interact with the Rails application using urllib to do HTTP requests, or use XML-RPC to just pull out data and then template that data into HTML within your Zope application using TAL.
Rails in front of a CMS
It sounds like your needs are more towards having Rails embedded in a CMS, but EnTransit is worth mentioning, as it enables you to easily version content out of Plone and into a relational database/XML representation.
Integration with CMS generating static pages (e.g. RedDot, Comatose)
RedDot
RedDot CMS publishes static html pages which can just be published into Rails’ public/ folder.
To have the application (Rails-) part of the site share the same look and feel as those static pages, let RedDot also generate your layouts to app/views/layouts.
Finally you can use RedDot to publish XML files which can then be parsed and stored in the database by your application. Useful e.g. for News or Product catalogs which need to be accessible via the Application, but should be edited in the CMS.
Comatose
Comatose is a Rails Plugin the would give you a “basic” CMS right from within your application. It enables users to CRUD pages with versioning capabilities. Comatose is highly configurable allowing it to integrate nicely with the application’s auth/auth system. Role based access to parts of the page trees can also be configured. No Image/File Uploads out-of-the-box. See Comatose file upload
Note
There is no comprehensive list of Rails Content Management Systems (in development or otherwise), so you’re going to have to use Google (or Yahoo, if that’s your thing).
Update: There’s a list of rails CMS apps at RailsBased.org – maybe a place to start your search
Rails Behind a CMS
What about using the CMS as a proxy? Create a custom Content Class for each of your Rails applications. Instances of that Class act as proxies and fetch data from the Rails application, depending on how different your Rails applications are, it may also be possible to get by with only one custom Content Class and each instance just holds the URL to the Rails app and any other relevant integration data. In this model, Rails is behind the firewall, so Rails only needs to do authorization as authentication can be trusted, or you could also do authorization in the CMS and have your Rails app be auth/auth free. You could either interact with the Rails application using urllib to do HTTP requests, or use XML-RPC to just pull out data and then template that data into HTML within your Zope application using TAL.
Rails in front of a CMS
It sounds like your needs are more towards having Rails embedded in a CMS, but EnTransit is worth mentioning, as it enables you to easily version content out of Plone and into a relational database/XML representation.
Integration with CMS generating static pages (e.g. RedDot, Comatose)
RedDot
RedDot CMS publishes static html pages which can just be published into Rails’ public/ folder.
To have the application (Rails-) part of the site share the same look and feel as those static pages, let RedDot also generate your layouts to app/views/layouts.
Finally you can use RedDot to publish XML files which can then be parsed and stored in the database by your application. Useful e.g. for News or Product catalogs which need to be accessible via the Application, but should be edited in the CMS.
Comatose
Comatose is a Rails Plugin the would give you a “basic” CMS right from within your application. It enables users to CRUD pages with versioning capabilities. Comatose is highly configurable allowing it to integrate nicely with the application’s auth/auth system. Role based access to parts of the page trees can also be configured. No Image/File Uploads out-of-the-box. See Comatose file upload