github-migration/engine
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a brand new CMS system with super sexy UI and cool features
46 Commits 13 Branches 7 Tags 15 MiB
Ruby 57.6%
Gherkin 12.2%
CoffeeScript 10.6%
SCSS 8.7%
Haml 6.2%
Other 4.7%
7ccc3d4548
Go to file
dinedine 7ccc3d4548 very simple api for contents (just create for now) + fix a lot of bugs in the custom fields plugin and some enhancements as well + add an ui for manage categories + fix bugs
2010-06-10 15:30:22 +02:00
app very simple api for contents (just create for now) + fix a lot of bugs in the custom fields plugin and some enhancements as well + add an ui for manage categories + fix bugs 2010-06-10 15:30:22 +02:00
config very simple api for contents (just create for now) + fix a lot of bugs in the custom fields plugin and some enhancements as well + add an ui for manage categories + fix bugs 2010-06-10 15:30:22 +02:00
db make an engine of the cms 2010-06-03 17:32:40 +02:00
doc very simple api for contents (just create for now) + fix a lot of bugs in the custom fields plugin and some enhancements as well + add an ui for manage categories + fix bugs 2010-06-10 15:30:22 +02:00
features make an engine of the cms 2010-06-03 17:32:40 +02:00
lib very simple api for contents (just create for now) + fix a lot of bugs in the custom fields plugin and some enhancements as well + add an ui for manage categories + fix bugs 2010-06-10 15:30:22 +02:00
public very simple api for contents (just create for now) + fix a lot of bugs in the custom fields plugin and some enhancements as well + add an ui for manage categories + fix bugs 2010-06-10 15:30:22 +02:00
script add cucumber to the projet (waiting for the first scenari) 2010-04-13 01:33:25 +02:00
spec rename CustomFields::CustomField into CustomFields::Field + create a dynamic class when we have an object with custom fields (optimization) + create a new type of custom field: categories + fix minor bugs + add ui to rename the alias of a custom field 2010-06-08 02:45:49 +02:00
tmp working stack ? 2010-04-09 11:23:41 +02:00
vendor/plugins very simple api for contents (just create for now) + fix a lot of bugs in the custom fields plugin and some enhancements as well + add an ui for manage categories + fix bugs 2010-06-10 15:30:22 +02:00
.gitignore rename CustomFields::CustomField into CustomFields::Field + create a dynamic class when we have an object with custom fields (optimization) + create a new type of custom field: categories + fix minor bugs + add ui to rename the alias of a custom field 2010-06-08 02:45:49 +02:00
.gitmodules working stack ? 2010-04-09 11:23:41 +02:00
config.ru first init 2010-03-30 00:01:47 +02:00
Gemfile rename CustomFields::CustomField into CustomFields::Field + create a dynamic class when we have an object with custom fields (optimization) + create a new type of custom field: categories + fix minor bugs + add ui to rename the alias of a custom field 2010-06-08 02:45:49 +02:00
Rakefile modify the way locomotive setups a mongo connection 2010-06-04 00:55:04 +02:00
README.textile fix some bugs about engine startup + add a generator to install assets into the parent app 2010-06-03 22:20:53 +02:00
VERSION rename CustomFields::CustomField into CustomFields::Field + create a dynamic class when we have an object with custom fields (optimization) + create a new type of custom field: categories + fix minor bugs + add ui to rename the alias of a custom field 2010-06-08 02:45:49 +02:00

README.textile 

h1. Locomotive CMS

Locomotive is a simple but powerful CMS based on liquid templates and mongodb database. If we have to give only 4 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
* inline editing

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. Installation

TODO

h2. Contact

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

Copyright (c) 2010 NoCoffee, released under the MIT license