The core BrowserCMS product offers features comparable to commercial CMS products. It is also extendable through dozens of community-developed and tested modules. With support for large teams of editors with variable permissions, it is an excellent option for developers looking for a powerful, scalable solution that allows complete freedom of design. Whether the site will be managed by development team or non-technical users, BrowserCMS allows for efficient site management without steep learning curves or expensive licensing and support.

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

  • It's just Rails: Each CMS project is a rails project that depends on the BrowserCMS gem. Developers can add new controllers, views, etc., just like any rails project.
  • Runs on Rails 3.2: Developers can use the latest APIs and features from Rails 3.2 on their BrowserCMS projects.
  • Direct in context editing: Users can browse their site to locate content and change it right on 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, allowing for rich designs that are still easy to manage by non-technical users. Developers can configure permission models and templates to ensure design integrity.
  • Sitemap: An explorer/finder style view of sections and pages in a site allows 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 that allows 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 highly configurable permission models that controls which users can edit, publish, or otherwise contribute. Content can be assigned to users for further editing or review.
  • Page Caching: Full page caching allows the web server (Apache) to serve HTML statically for any pages that have not changed, reducing server load.