engine

a brand new CMS system with super sexy UI and cool features

Go to file

dinedine 282fbb7244 merging		2010-10-14 14:37:14 +02:00
app	fixing failed tests	2010-10-12 17:26:05 +02:00
autotest	Fixing up dependencies (httparty/crack) and adding autotest	2010-07-25 18:59:03 -07:00
config	merging	2010-10-14 14:37:14 +02:00
db	Cleaning whitespace on all .rb files so commit diffs from now on will be a bit more readable	2010-07-23 13:09:54 -07:00
doc	check tasks done	2010-10-14 10:59:04 +02:00
features	editable_file tag is implemented + remove not used editable elements all in once for better performance + default content inherits from the content of the parent element	2010-08-31 23:53:30 +02:00
lib	merging	2010-10-14 14:37:14 +02:00
perf	fix a lot of tiny bugs (not yet) + testing import tool	2010-09-27 00:31:50 +02:00
public	polish the import module + some code refactoring / cleaning	2010-10-12 02:12:18 +02:00
script	add cucumber to the projet (waiting for the first scenari)	2010-04-13 01:33:25 +02:00
spec	fixing failed tests	2010-10-12 17:26:05 +02:00
.gitignore	merging	2010-10-14 14:37:14 +02:00
.gitmodules	bump gem version + reset gitmodules	2010-07-13 23:17:56 +02:00
config.ru	first init	2010-03-30 00:01:47 +02:00
Gemfile	merging	2010-10-14 14:37:14 +02:00
Gemfile.lock	merging	2010-10-14 14:37:14 +02:00
LICENSE	specify MIT license + textile filter + fix bug with new tree plugin + fix tests	2010-07-06 17:00:02 +02:00
locomotive_cms.gemspec	Vendoring mongo_session_store so we have one less dependency	2010-09-28 02:19:55 -07:00
Rakefile	Updating dependencies, removing jeweler, and cleaning up gemspec	2010-09-27 23:04:40 -07:00
README.textile	first and unfinished draft of the import tool	2010-09-23 00:59:30 +02:00

README.textile

h1. Locomotive CMS

Locomotive is a simple but powerful CMS based on liquid templates and mongodb database. At my company ("NoCoffee":http://www.nocoffee.fr), we use it for our clients when they request a simple website.

If we have to give only 5 main features to describe our application, there will be:

* managing as many websites as you want with one application instance
* nice looking UI (see http://www.locomotiveapp.org for some screenshots)
* flexible content types
* playing smoothly with Heroku and MongoHQ
* inline editing (beta)

h2. Strategy / Development status

We already developed a fully functional prototype in Rails 2.3.2 with both active record / mongomapper and it worked quite well. We are even using it for some client websites.
Now, our goal is to port our prototype to Rails 3 and migrate from mongomapper to mongoid. Besides, we put a lot of efforts to make it as robust as we can by writing better specs than we wrote for the prototype at first.

h2. Gems

Here is a short list of main gems used in the application.

* Rails 3.0
* Mongoid 2.0.0.beta 17 (with MongoDB 1.6)
* Liquid
* Devise
* Carrierwave
* Haml
* Delayed job

h2. Installation

See the "official website":http://www.locomotiveapp.org

h2. Team

* Developers: "Didier Lafforgue":http://www.nocoffee.fr, "Jacques Crocker":http://www.railsjedi.com
* UI Designer: "Sacha Greif":http://www.sachagreif.com

h2. Credits

"Rodrigo Alvarez":http://blog.codecaster.es/ for his plugin named Congo which gave us a good starting point and for his availability for (very late) tech discussions.

"Emmanuel Grard":http://www.grardesign.com designed the awesome locomotive illustration in the LocomotiveApp.org landing page.

h2. Contact

Feel free to contact me at didier at nocoffee dot fr.