Radiant CMS

A new version of our favorite Ruby on Rails CMS has been released, Radiant CMS 0.9.0. Obviously, I spoke a little too soon last October when I announced that 0.9.0 was coming soon. Each open source community has their own pace and time-line for releasing the release candidates of their software. In retrospect, I should have noted that Radiant CMS developers like to take their time in making sure the Radiant releases are at a level of quality and stability they're comfortable with before releasing the final versions to the general public.

A new version of Radiant, a Ruby on Rails content management systems, is coming soon. Radiant 0.9.0 has just been released as a release candidate.

In this release the interface for the CMS has been updated to make Radiant more stylish and compact. Apart from the stylistic changes, there are a few other significant changes to the user interface worth mentioning:

Radiant 0.8.0 was released. While not that exciting of a release, at least it gives me something to talk about with regards to the Radiant CMS.

Radiant 0.8.0 “Asterism” features a brand new and more compliant caching mechanism based on Rack::Cache, and numerous bugfixes and small enhancements. Also included are:

• An extensive integration suite using Cucumber and Webrat
• Rails 2.3.2 (previously 2.1.2)
• Highline 1.5.1
• Haml 2.0.9

Additional development news can be found about Radiant CMS on their blog.

Occasionally, I see a post that I have written as a reference in a white paper, a book, or somewhere else online.  I actually started CMSReport.com as a place for me to learn more about Web content management systems and information systems.  Whenever someone references CMS Report it signals that we have gone full circle where someone is also learning from me.  There is not a more awesome feeling than this.

One thing I have yet to achieve is being a legitimate reference at Wikipedia.  Until now!  CMS Report is being referenced on the wiki page for Frog CMS.

Radiant, a Ruby on Rails based CMS, will soon be released under version 0.7. The new version is currently available as a release candidate. 

The most significant changes between Radiant 0.6.9 and 0.7 will include:

Radiant 0.6.6 was released over the weekend, shortly after the release of Radiant 0.6.5.  Obviously, 0.6.6 of this built with Ruby on Rails CMS was released to fix some bugs in 0.6.5.  So instead of focusing on the bugs, let's focus on what is new in 0.6.5/6 since Radiant 0.6.4 was released in November 2006.

Since Radiant 0.6.4, the latest versions of the software introduced two major changes:

• Rails 2.0.2 included (0.6.4 used Rails 1.2.5)
• RSpec 1.1.4 is used in core and supported in extensions

It was announced at RadiantCMS.org that the latest version of their CMS was released, Radiant 0.6 (Lapidary).

Last night the core team finished polishing off the rough edges of the latest release of Radiant. This is the first serious release in well over 6 months. The big news in this release is that we have created a first-class extension system to make it easier for you to tailor Radiant to meet your needs. A lot of people have already started using the extension system to create a number of useful third party add-ons. There are also numerous bug-fixes and improvements in other areas of the application. If you are still on the 0.5.x series this upgrade is a must. Core team member Sean Cribbs has compiled a complete list of the changes over on his blog.

End users and site managers will notice improvements and new features:

Philippe Archambault wrote to us that he is working on a PHP version of Radiant CMS. Radiant CMS is based on the Ruby language. Mr. Archambault has appropriately named his CMS, phpRadiant. If imitation is a sincere form of flattery, then lets hope the Radiant CMS folks are blushing!

Mr. Archambault isn't the first person to suggest taking what they liked in Radiant CMS and migrating it from the Ruby language to one that is PHP based. However, his project is the first one that I know about which has actually seen the light of day.

I always find these type of stories ironic. Last week, I had someone make a comment to an old article I wrote on the Radiant CMS. For those liking Radiant, the commenter remarked "give cakePHP a trial run if you want a cms similar to this but in PHP". One of the reasons I chosen to discuss Radiant was that it was built with Ruby on Rails.

The past couple days has been a busy time for those involved in the Rails open source project. Just as busy as the Rails core developers were the users running Ruby on Rails applications (such the Radiant content management system). On Wednesday, the project's developers released Rails 1.1.5. In the announcement of the Rails release, David August called upgrading the new version "mandatory" since the security vulnerability was so severe.