Case Study: Refinery Web Content Management System

If at first you succeed, try, try again. 

Business goals
We developed our original Ruby on Rails content management system (CMS) back in 2003 because we couldn't find a good alternative. It was praised for ease of use but it wasn't easily extendable. So we set out to create a modular version (rebranded as Refinery CMS) and release it to the open source community. This is our strategy to make it better and give something back.

User objectives
Having seen our first generation CMS in action, we listened to and learned from real live users. They tend to repeat a set of common tasks and want them to be as easy as possible. At the same time, their needs are unique so they expect to use the special functions their site requires. 

Our approach
Refinery CMS is based on plug-in modules that extend the functionality according to the specific needs of each client. Because clients don't get what they don't need, their CMS isn't bloated with a lot of useless features.

The application is designed to:

• Make content management as easy as possible. 
  Focus on the primary needs of small business websites  

• Provide extensions to meet each client's needs.
  Add only those functions that are going to be useful

• Continually improve as an open source solution.
  Any developer can contribute to make Refinery better

Results
We've already completed a handful of sites using Refinery and we're preparing it for release in Spring 2009. If you're interested we'll notify you when Refinery goes live.

Send me news about Refinery's release or request a demo.