ComfortableMexicanSofa is an MIT-licensed content management engine, distributed as a Ruby gem, that drops into an existing Ruby on Rails 5.2+ application to provide a self-contained admin area, page templating and multi-site content management without the CMS intruding on the rest of the codebase.

What it is

ComfortableMexicanSofa is a Rails Engine — a packaged slice of an application that mounts into a host Rails app — published as the comfortable_mexican_sofa gem and tagged in this registry under cms, rails, rails-engine and ruby. Rather than running as a separate application alongside your code, it installs into the Rails project itself, adds its own database migrations, and attaches two route sets: one for the admin area and one for serving content. The README describes the integration as a "simple drop-in" requiring minimal configuration, and states explicitly that the CMS stays away from the rest of your application.

The concrete problem it solves is the gap between a Rails application and editable web content. Instead of hand-building an administrative interface for pages, layouts and uploaded files, or standing up a separate CMS product and then reconciling two codebases, a team adds the gem and gets a Bootstrap 4 admin area, a page model built from Layouts and Pages, and a templating layer that renders stored content into the host application's routes. Content authors work in a browser at /admin while developers keep working in the Rails codebase they already maintain.

Key capabilities

• Drop-in Rails Engine integration mounted through comfy_route :cms_admin, path: "/admin" and comfy_route :cms, path: "/", with the content-serving route required to sit last in config/routes.rb.
• Page templating through Content Tags, so a Layout can mix reusable markup with editable regions such as {{ cms:text title }} and {{ cms:wysiwyg content }}.
• Multiple Sites from a single installation, where each Site defines a hostname, a content path and a language.
• Multi-language support (i18n) across locales including ca, cs, da, de, en, es, fi, fr, gr, hr, it, ja, nb, nl, pl, pt-BR, ru, sv, tr, uk, zh-CN and zh-TW, plus per-page localization.
• CMS Seeds for populating initial content, and Revision History for reverting changes to content over time.
• An extendable admin area built on Bootstrap 4, using CodeMirror for HTML and Markdown highlighting and Redactor as the WYSIWYG editor.
• File attachments handled by ActiveStorage, image resizing via ImageMagick, and pagination through either kaminari or will_paginate.

Who uses it and how

• Rails teams that want editorial control over marketing or documentation pages without introducing a second application, a second deployment or a second user database.
• Operators running several hostnames from one Rails deployment, using the Multiple Sites feature to give each site its own content path and language.
• Multilingual publishers who need localized pages across the twenty-plus locales the engine ships translations for.
• Agencies and teams that provision a fresh environment repeatedly, using CMS Seeds to populate baseline content rather than recreating pages by hand.
• Developers who need to extend the admin area itself, which the README documents as reusable through its "Reusing Admin Area" guide.

Getting started

Add gem "comfortable_mexican_sofa", "~> 2.0.0" to the Gemfile, run bundle install, then rails generate comfy:cms and rake db:migrate from the Rails project root, followed by rails active_storage:install so attachment migrations are available.

How it compares

No list of paid or proprietary products that this project replaces is provided in the facts, and no comparable tools are named, so it stands alone in this registry. The relevant contrast is structural rather than competitive: it is an MIT-licensed engine that lives inside a Rails application, not a standalone CMS product with its own hosting stack.

When to use it — and when not

Choose it when the host application is already Rails 5.2 or newer and the team is comfortable owning the operational surface it pulls in: ActiveStorage configuration and migrations, an ImageMagick installation, a pagination gem added to the Gemfile, and a database that supports the engine's migrations. It is a poor fit for non-Ruby stacks, for applications pinned below Rails 5.2, or for teams wanting a CMS they can run without a developer in the loop — the README is a short quick-start that defers most detail to the project wiki, and the default admin credentials of username and password must be changed in the initializer immediately after installation.

gem "comfortable_mexican_sofa", "~> 2.0.0"

bundle install
rails generate comfy:cms
rake db:migrate

comfy_route :cms_admin, path: "/admin"
comfy_route :cms, path: "/"

<html>
  <body>
    <h1>{{ cms:text title }}</h1>
    {{ cms:wysiwyg content }}
  </body>
</html>