We have just released version 2.0.4 of Refinery CMS. This release builds on our previous releases and adds many improvements and bug fixes.
Importantly, we have fixed a security issue which means if you are running any previous builds in the 2.0.x release that you should upgrade to 2.0.4 as soon as possible.
If you're at Railsconf 2012 in Austin, we should get together!
Tom Brooke has booked us a slot at BohConf on Monday from 2 to 3pm in room 406/408. If you can show up, awesome! If not, feel free to say hi to Rob Yurkowski in the halls — he's the rather tall guy with a white cap.
Hope to see you tomorrow!
The Refinery core team is immensely proud to announce the addition of Rob Yurkowski!
Rob has been working really hard behind the scenes since before the release of version 2.0.0 and he was instrumental on getting it out on time. He's kept our whole team focused on the next version, has collated our feature requests and issues, has been working on updating our documentation, and has also been performing a lot of support on the mailing list. In short, we love him!
Rob is a developer with Dynamo...
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.
It's been just under three years since David Jones changed Refinery CMS from being a closed source project...
Following in the vein of great blog posts to help you use the "edge" version of Refinery CMS, which will be released this month, is an awesome post from Josef.
You can see it over at his blog in a post titled "ZOMG! Refinery 2 Now as Mountable Engine!"
Thanks, Josef!
There has been a significant amount of development toward version 2.0.0 of Refinery CMS and it's shaping up to be a really great version but until then it may not seem straightforward to actually use this version. Tony Semana has written a walkthrough titled "Installing RefineryCMS with Rails 3.1.3" which described the process of setting up a new website with the upcoming 2.0.0 version of Refinery CMS. Thanks, Tony!
We love it when people use Refinery CMS as it is being developed but...
Uģis: "Thanks to all of you who donated for my trip to RubyShift and RubyC. RubyShift was a great experience for me - for the first time traveled all by myself, met some Refinery CMS users/fans, listened to great talks and to sum it up - those 4 days while I was in the Ukraine I had a really great time.
Unfortunately I'm not going to attend RubyC because of some work related issues so all of you who donated for RubyC I want to say sorry and thank you!
Remember to stay awesome!"
Recently...
We are planning on holding a "Refinery CMS Day" on the 30th of July. The purpose of this day is to fix as many issues related to Refinery CMS as possible so that we can support Rails 3.1 when it is released. Head over to GitHub issue list to see currently reported issues and let us know if you're able to help on any of them.
Translation revisions are also more than welcome. Currently Refinery CMS is translated into 22 languages so it would be really cool if all of those translations...
It was only the 27th of February of this year, 2011, where we posted about hitting 100 contributors and now we have 150!
As the lead developer of Refinery CMS, every new contributor makes my life easier and makes the product better so I just wanted to take the opportunity to express my gratitude.
THANK YOU to all of you!
Today the Refinery CMS Core Team is announcing Refinery CMS version 1.0. You can get it here.
It is exactly 2 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.
Phil Arndt joined Resolve Digital shortly before the public release. He picked up what was there and took it to the next level (and then some). During this time it was hard not to see Phil's name mentioned as...