refinery/refinerycms

An extendable Ruby on Rails CMS that supports Rails 6.1 to 8.1+ and Ruby 3.x to 4.x

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 57 minutes ago
Added to GitGenius on September 17th, 2026
Created on May 28th, 2009
Open Issues & Pull Requests: 35 (+0)
GitHub issues: Enabled
Number of forks: 1,223
Total Stargazers: 3,905 (+0)
Total Subscribers: 109 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 30.5 hours
Mean response time: 28.5 days
90th percentile: 72.9 days
Tracked items: 12

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 955 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Refinery CMS is a content management system built as a Ruby on Rails engine that supports Rails 6.1 through 8.1 and Ruby 3.x through 4.x.

The tool addresses the need for a CMS that non-technical end users can operate without overwhelming complexity. Rather than forcing clients to learn specialized interfaces or templating languages, Refinery integrates directly into Rails applications and follows Rails conventions. It provides a visual page editor for managing site structure and content, image and file upload capabilities backed by Dragonfly with Amazon S3 support, user authentication and permission management through Devise, and an extension system allowing developers to add custom functionality beyond what ships out of the box.

Refinery suits projects where clients need self-service content management capabilities without extensive training. Developers benefit from working within the Rails ecosystem rather than learning a separate system; the tool emphasizes following Rails conventions and does not impose custom templating languages. The extension architecture lets you build domain-specific features on top of the core CMS. This approach works well for sites with straightforward content needs where the priority is ease of use for non-technical administrators rather than complex workflow management.

The project maintains active support across recent Rails and Ruby versions, indicating ongoing compatibility work with the latest platform releases. Documentation is housed in the repository's guides folder rather than an external website, reflecting a shift toward keeping information alongside the code. The README acknowledges that some documentation has become outdated, suggesting the maintainers are aware of documentation gaps and working to consolidate guidance in the repository itself.