// the take
Camaleon CMS is a Rails gem that turns an existing Rails app into a WordPress-style CMS, with custom content types, fields, themes and plugins defined without writing migrations by hand. It's aimed at Ruby/Rails teams who want CMS-style content management without adopting a separate PHP stack or a headless CMS service.
It installs as a gem into an app you already have rather than forcing a dedicated standalone install, which matters if you're bolting a CMS onto an existing Rails product. The plugin/theme system is a real hook mechanism (config.json registration, a mutable args payload passed through named hooks like after_login, user_before_register) rather than a thin wrapper, so extension points are documented and discoverable. It ships multiple cache layers (content cache, query cache, asset manifests) baked in rather than left to the integrator. CI runs against a matrix of current and experimental Rails/Ruby versions, which is a decent signal the gem is kept compatible rather than frozen against one stack.
The actual WYSIWYG/visual editor is a paid plugin, not core — for a CMS whose whole pitch is content editing, gating the editor behind a purchase is a meaningful gap for adopters expecting WordPress-level out-of-box editing. The plugin and theme ecosystem is thin and mostly single-author (owen2345, a couple of other contributors) rather than a broad marketplace, so you're trusting one or two maintainers for anything beyond the default theme. Support channels are Gitter/Skype/email to the author rather than anything resembling an SLA or active community forum, which is a bus-factor risk if you're putting this into a production content pipeline. It also pulls in a full Rails stack plus ImageMagick and a relational DB migration step at install time, so it's heavier to bring into a project than a standalone or headless CMS would be.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →