Radiant CMS is all about making a beautiful and simple content management system. Most people feel comfortable with the Radiant interface from the first time they see it – mostly because of the lack of any complex features and providing a sense of simplicity. But, once you start using Radiant for a real web site of any size, the lack of some advanced features poses a problem. Such simple tasks as re-ordering pages or uploading images is not built into Radiant, but luckily this is easily overcome by installing the appropriate extensions.
While future articles will explain how to build your own Radiant extensions, this article is essentially a catalogue of some useful general-purpose Radiant extensions. The extensions are ordered from how important the author considers them to be, starting with the extensions that should be part of virtually any Radiant installation. See below for instructions on how to install extensions and on how to try out the demo application built for this article. The extensions have all been tested using Radiant CMS 0.7.1 from a gem install with an SQLite database.
Let's look at some basic but really useful extensions that provide great value.
If you build menus dynamically from the pages created in Radiant (e.g. by using Navigation Tags mentioned below), the Reorder extension is a must. The extension adds a database field to keep track of the ordering of pages in the page tree, and it adds arrows in the user interface to let the web master change this ordering. It also ensures that the pages will be returned in the specified order by default.
Since Radiant does not include any asset handling, several extensions exists to allow the web master to upload, manage and display images, videos, documents and other types of files. The Page Attachment extension - based on the attachment_fu plugin - is widely used and supported, but I recommend the newer and more user-friendly Paperclipped extension for this task. It is based on the paperclip plugin, and it allows the web master to easily upload and insert assets while editing a page. Further, it adds an "Assets" tab providing an overview of all uploaded assets and the ability to filter and search through assets.
The Copy/Move extension is, like Reorder and Paperclipped, an extension you can hardly go without on a production web site. It allows the webmaster to copy a page, with or without children or to move the page somewhere else in the page tree. Without this extension the web master is reduced to manually copy page content when the site structure is refactored, which is not something anyone should endure.
Extensions for the Developers
While the first set of extensions were for the benefit of the web master, we now move on to some extensions aimed at the developer(s) of the web site.
You can generate static navigation menus in Radiant using the built-in <r:navigation> tag, and you can also generate a menu that changes dynamically with the page tree using a variety of Radius-tags. The former approach is not well suited unless the web master knows where and how to edit the static menu, and the latter might be a bit complicated for newcomers to Radiant. One solution is to use the Navigation Tags extension. It adds an <r:nav> tag which will render pages on a certain level in the page tree, or the entire page tree if need be, taking supplied options into account.
This extension will help developers to stay DRY (Don't Repeat Yourself) when building the website. Any site beyond the very basic will have certain variations to the layout of different pages and sections, and while this can be solved by clever use of page parts and snippets to a certain degree, making multiple Radiant layouts will often be a more intuitive solution - especially from the point of view of the web master. Without Nested Layouts you will need to separate any code shared between layouts into snippets that you include in each layout, but with this extension you can make a master layout with the basic markup required by all pages, and then create several child layouts with variations in the design.
Styles and Scripts
Radiant's built-in workflow support is limited to setting the status of each page to either draft, reviewed, published or hidden, and this is enough in most cases. However, once a web site is running it is not possible to work on a new draft of a page while still having the old page displayed. The Concurrent Draft extension changes this and allows the web master to work on a draft and schedule when the new version of the page should be promoted to the live website to be visible by all. The extension does not add real versioning of pages, but it improves the workflow to be more suitable for medium and large web sites.
The last extensions mentioned in this article are more of a technical and advanced nature.
You can add your own models, controllers and views to a Radiant web site, preferably by building your own extensions specific to your site, something that will be explained in future articles of the Rails Magazine. Once you start building your own dynamic pages running along-side your static Radiant pages, you will face the need to use the same layouts across all pages, dynamic or static. Share Layouts allows you to refer to a Radiant layout instead of Rails layout in your custom controllers by means of the radiant_layout 'layout name' command. This way, you still have full control over the layouts and menus from Radiant, even for your dynamic pages.
Once you have your Radiant site in production, you will want to be notified of any errors that occurs on the site. Even if you haven't added any custom code to Radiant, a lot of things can still go wrong. The Exception Notification extension wraps the widely used plugin of the same name, but adds the Internal Error page type, which gives you full control of the page shown when errors occur within Radiant. The extension requires ActionMailer to be enabled (disabled by default by Radiant) and it needs to know where to send e-mails to. This is all explained in detail in the readme file bundled with the extension.
Radiant has a database table where it stores configuration such as the title displayed in the administration pages and what parts to add as per default to new pages. Many extensions also add their configuration to this table. Normally you would have to change these settings using the console, but the Settings extension adds a tab where the configuration can be edited directly from the browser. This makes life easier if you have to change configuration settings on a regular basis, or want the web master to be able to change them easily.
Installing a Radiant extension
To install a Radiant extension, you will need to have a console open at the root of Radiant CMS-based Rails application. Extensions that are registered in the Radiant CMS Extension registry can be installed as easily as a Rails plugin with the command:
script/extension install [extension name]
For extensions not in the registry, you will need to manually download/clone them into the /vendor/extensions/[extension name] and run these commands:
rake radiant:extensions:[extension name]:migrate
rake radiant:extensions:[extension name]:update
Once you deploy your application, you will probably also need to run migrations for all of the installed extensions (unless you start out with a clone of your development database). This can be done by running the following command on the server:
rake RAILS_ENV=production db:migrate:extensions
Sample Demo application
You can easily try out all the extensions and see them in action by cloning the demo application that has been made available on Github. You will need to have the Radiant gem and the SQLite gem installed (the latter is not necessary if you know how to change the application to use another database system), which is also shown below. Finally, you will need to bootstrap Radiant, migrate all the extensions and start the server. The following set of commands show how to do it:
gem install radiant
gem install sqlite3-ruby
git clone git://github.com/RSpace/railsmag-radiant.git
git submodule init
git submodule update
At this point we have the Radiant application locally, but the database is not initialized. One little snag with Radiant extensions is that they most often need to be disabled in order for Radiant to be able bootstrap the database. This is because Radiant will load the extensions before executing any rake tasks, and extensions relying on something in the database, typically the config-table, will fail.
So, open config/environment.rb and remove the comment at the config.extensions =  line. Now bootstrap the database:
Now, out comment the line again in config/enviroment.rb. Migrate all the extensions, and finally; start the server and open the site http://localhost:3000 in your browser:
There are more great extensions out there, many of which adds specific functionality to Radiant such as managing a picture gallery or sending out newsletters. Some can be found at the Radiant extension registry, but I also recommend doing a search for "radiant extension" on Github in your search of useful extensions.