BrowserCMS: Humane Content Management for Rails
Ruby CSS JavaScript
Latest commit d654557 Oct 1, 2014 @peakpg peakpg Bump for RC1 status
Failed to load latest commit information.
app Disable browser caching for entire CMS to avoid users submitting or s… Jul 30, 2014
bin [Devise] Refactor to use as Authorization Dec 16, 2013
config [Fix #723] Deleting Form Entries works Jul 16, 2014
db [#659] Fix - Improve large site map performance Jan 22, 2014
doc Link to fixed bugs Mar 11, 2014
features [Fix #723] Deleting Form Entries works Jul 16, 2014
lib Bump for RC1 status Sep 30, 2014
script Make engine generators work correctly. Dec 18, 2013
spec [Closes #682] Improved :name input Jan 30, 2014
test [Fixes #556] Templates uniqueness for names Mar 11, 2014
vendor/assets/javascripts [#487] Upgrade CKeditor Mar 14, 2012
.gitignore * Properly ignore .ruby-version Jan 30, 2014
.ruby-gemset [Fix #723] Deleting Form Entries works Jul 16, 2014
.travis.yml [#651] Upgrade and test w/ Ruby 2.0 Jan 17, 2014
.yardopts Add rake task for generating YARD doc's locally. Fix warnings for YAR… Apr 25, 2011
COPYRIGHT.txt Add icomoon icon for homepage Oct 30, 2012
GPL.txt Added initial version of License (LGPL), GPL and copyright notice. Feb 25, 2009
Gemfile Loose dependency on paperclip to allow for older versions as needed. … Sep 30, 2014
Gemfile.lock Bump for RC1 status Sep 30, 2014
LICENSE.txt Added initial version of License (LGPL), GPL and copyright notice. Feb 25, 2009
README.markdown * Updates README for 4.0 Jan 17, 2014
Rakefile [Fixes #657] Can no longer delete homepage. Mar 11, 2014
browsercms.gemspec Loose dependency on paperclip to allow for older versions as needed. … Sep 30, 2014


BrowserCMS: Humane Content Management for Rails

BrowserCMS is a general purpose, open source Web Content Management System (CMS) that supports Ruby on Rails v4.0. It can be used as a standalone CMS, added to existing Rails projects or extended using Rails Engines. It is designed to support three distinct groups of users:

  1. Non-technical web editors who want a humane system to manage their site, without needing to understand what HTML or even Rails is.
  2. Designers who want to create large and elegantly designed websites with no artificial constraints by the CMS.
  3. Developers who want to drop a CMS into their Rails projects, or create CMS driven websites for their clients.


BrowserCMS is intended to offer features comparable to commercial CMS products, which can support larger teams of editors. This means having a robust set of features as part of its core, as well as the capability to customize it via modules.

Here's a quick overview of some of the more notable features:

  • Standalone CMS: BrowserCMS is designed to provide a robust CMS capabilities out of the box for content heavy web sites.
  • Mobile Friendly: Sites can be built to use mobile optimized designs that are optimized for small screens, with low bandwidth, with responsive design.
  • In Context Editing: Users can browse their site to locate content and make changes from the page itself.
  • Design friendly Templates: Pages aren't just a template and giant single chunk of HTML. Templates can be built to have multiple editable areas, to allow for rich designs that are still easy to manage by non-technical users.
  • Highly Extensible: Developer have access to the full Rails development stack, and can customize their project by adding their own controllers, views as well as CMS content types.
  • Sitemap: An explorer/finder style view of sections and pages in a site allowing users to add and organize pages.
  • Content Library: Provides a standardized 'CRUD' interface to allow users to manage both core and custom content types.
  • Content API: A set of behaviors added to ActiveRecord which allow for versioning, auditing, tagging and other content services provided by the CMS.
  • Section Based Security: Admins can control which users can access specific sections (public users), as well as who can edit which pages (cms users).
  • Workflow: Supports larger website teams where some users can contribute, but not publish. Users can assign work to other publishers to review.
  • Page Caching: Full page caching allows the web server (Apache) to serve HTML statically when they don't change.
  • CMSify your Rails App: BrowserCMS can be added to existing Rails applications to add content management capabilities.

Getting Started

See the Getting Started guide for instructions on how to install and start a project with BrowserCMS.


BrowserCMS is released under a LGPL license, and is copyright 1998-2014 BrowserMedia. The complete copyright can be found in COPYRIGHT.txt, and copy of the license can be found in LICENSE.txt.

Documentation / Support

The user documentation and guides for this version of the application can be found at:

  1. Guides and Wiki
  2. API Docs
  3. Report a Bug!
  4. Discuss the Project
  5. BrowserCMS Site