Ruby CMS Like Drupal

As full-time Drupal developers by day, and Ruby enthusiasts by night, we believe the creation of a similar content management system which delivers functionality similar to Drupal is only a matter of time, and that time is now. The CMS we have begun to create is named Evolution CMS, a Ruby-based, modular content management system.

Why Create A Ruby CMS Like Drupal?

We love Drupal and Ruby.

ALPHA Release Goals

Current features which will be within the initial ALPHA release.

  • Module infrastructure
  • Core JavaScript (jQuery, UI, several plugins)
  • Administration theme similar to Habari
  • Menu system
  • Theme system
  • Form API
  • Command line utility (for creating Evolution CMS instances, creating translations etc)
  • Node module
  • System module
  • User module
  • Logging system / module

Stay Informed

Too keep up to date with Evolution CMS subscribe to our feeds.

Early Contribution

Although we are in early development phases, please leave comments below discussing anything you would like to see in the ALPHA release of Evolution CMS.

Comments

Well this is a fantastic idea and i will be waiting for it .

Interesting news indeed. Any improvements yet? And may I ask, what will be the advantage of Ruby over PHP?

There will certainly be many public betas of the ruby CMS when we feel it is at the right point. At the moment we would just be bombarded with feature requests and bug fixes that we are already aware of so it would only slow down development.

This should be one of the more interesting topics to come into the CMS world this year. I was wondering if there is a public testing planned, and if I can be part of it, please?

I dont know programming but ruby + drupal will surely motivate me to learn programming...

hope this project doesn't die out

Personally there would be not much benefit in utilizing rails for this project in my opinion. We are looking to create a cms with very good performance, extremely low learning curve, and minimalistic core library. Everyone is starting to abstract functionality into gems more and more lately so its pretty easy to pick and choose which components we need, not to mention since each package must be compatible with core we cannot be ORM agnostic, etc.

Currently the libraries we are using are:

1. Sinatra / Rack
2. DataMapper
3. jQuery / jQuery UI

> ...we have no intention of integrating with Rails...

I'm not pushing Rails or anything but that sounds like a pretty strong stance. Can you give a little more detail as to why you're so strongly in the "non-Rails" camp? Just curious I guess.

Thanks for your suggestions. To be quite honest we have no intention of integrating with Rails. Many of the things you mentioned will most likely take the form of 'Packages', which is what we have decided to call our modular system, as not to be confused with ruby Modules, however multi-lingual support, multi-domain support, and most likely search will certainly be part of the core package.

Among other things we will also be including jQuery and jQuery UI within core, making all of its fantastic UI components available to Package developers without any issues.

I want to see
1. Evolution cms install on rails such as plugin. For example railfrog.
2. multilanguages
3. multidomains. tree of domains. such as typo3
4. easy RSS and Atom
5. search
6. Google Sitemap generation
7. pdf generation
8. easy way to install and write extensions
I hope that Evolution cms will be the best cms on ruby. Because existing cms on ruby doesn't make all features that developer want.

When will this be released?

Thank you for your interest! It will certainly be an amazing project when it is nearing completion, this will take quite some time unfortunately, but the Ruby community will certainly here about it when Evolution CMS becomes available.

Until now, I used drupal, joomla and some other CMS, and found what I really want is a system that I can understand and be familiar with. The above systems are all good, but they all make me feel helpless when I look at the the php code, which I don't quite understand, every time I met an error.

And I also tried some CMS that based on ruby or RubyOnRails, like Radiant, Rubricks.
Rubricks has a lot of features, but I do not like the design of it.
And Radiant's design is good, but its features is a little bit limited.

And finally, I found myself here.
If you are about to create a cms like drupal and have the design like the admin picture you provide, 'EVO' is exactly what I want.
I looking forward to see your release and hope that I can contribute some on the following component.