github.com/aceofspades/caloris) is a file-based Content Management System back-end built as a[Caloris](
Rails 3.1 Engine.
The [Caloris Basin](en.wikipedia.org/wiki/Caloris_Basin), an impact crater on the planet Mercury, is one of the largest in the solar system.
By using the file system for storage instead of a database, content can be easily managed with standard text editors, while the Mercury Editor front-end cn be used by non-technical staff. Version control can be leveraged, as with source code, to handle deployments of site content and history.
A CMS for Rails should:
Be an Engine, so that you do not have to build your app around it, nor change the way your app works
Be simple until a more complex site warrants something different
Leverage what is already used or known, i.e. git for version control
Be easy for non-technical users, while not being cumbersome for the technical
Mainly inspired by the [Mercury Editor](jejacks0n.github.com/mercury/).
The author was discouraged buy a high complexity-to-performance ratio of available Rails CMS approaches. Mercury Editor has a great philosophy: provide a great WYSIWYG front-end rather than to create an end-to-end solution that might not be useful in all cases. Caloris takes over where Mercury leaves off to provide a solid back-end.
Components of a full-blown CMS might be:
Front-end, Mercury Editor
Version control, git
For an example application, check out test/test_app.
Inpired and made possible by [Mercury Editor](jejacks0n.github.com/mercury/).
Distributed under the MIT License, copyright © 2012 PENSCO LLC.