Refinery CMS 2.0.0 released

2 minutes and 55 seconds read.

The Refinery CMS Core Team is proud to announce the release of version 2.0. You can get it over at the download page.

Refinery 2.0 makes a number of very important updates to the project. Chief amongst these, Refinery now supports Rails 3.2 and the asset pipeline, and is now mountable as a Rails engine. You can see a list of the most notable changes in the change log.

Refinery's Journey

It's been just under three years since David Jones changed Refinery CMS from being a closed source project at Resolve Digital to an open source project for us all to enjoy. Nearly a year ago, Refinery 1.0 was released, and since then, many sites have been built upon those steady foundations.

The intervening year has seen some change in Refinery's codebase and core team. A few stats: Refinery has now exceeded 2,000 followers, and is rapidly approaching 600 forks. We have 214 contributors, all of whom have made a huge difference.

We've also raised over $1,500 toward the development of Refinery, so a big thank you to all of you who have donated!

Philip Arndt is now the chief maintainer of Refinery. He maintains his impressive commit count and frequency (missing a contribution on only two days of the past two months when he was at Rails Camp NZ with no Internet).

Since joining the core team on the release of 1.0, Uģis Ozols has also maintained a heavy commit count, and is now the second-most frequent committer to Refinery. He has a masterful command of the framework.

However, we are also sad to announce that two of our core team members are no longer active within the project:

David Jones is no longer involved in the day-to-day maintenance and Steven Heidel is very busy with his studies and his own web practice, and can no longer actively contribute to Refinery.

Beyond 2.0

There are plans for a 2.1 and a 2.2 release. Refinery 2.1 will focus on the addition of new features. To name a few:

  • Refinery will be refactored and made more lightweight;
  • Support for alternative WYSIWYG editors;
  • A more accessible Menu API; and
  • Supporting Disqus comments on RefineryCMS-blog

Refinery 2.2 will largely be a house-keeping release. At this point, we will re-evaluate all the features inside of Refinery, and try to trim the code base. Refinery 2.2 will also set up the transition from 2.x to 3.0.

Finally, we'd like to again thank every contributor to the Refinery. We're very proud of the project and how far it has come.

-- The Refinery CMS Core Team