At last, I launched it, thanks to Sacha’s help ! Of course, it is not as perfect as I wish. But, I think it represents a good start and I have a ton of new features to add. There are so many things to say about the CMS and how I see its future…

The documentation section looks empty but do not worry, I’m working hard on it.

“First come, first serve”. My CMS has been “approved” (by me) since I used it to run 3 websites including this one on Heroku (Heroku/MongoHQ are so awesome). I will post urls and some screenshots about them later.

I’d be very pleased to hear your ideas, comments and even critics.

We are exciting to announce you that Jacques (aka Railsjedi in the Ruby on Rails community) joined us two weeks ago on Locomotive.

He is a great developer and has a clear vision about how has to be managed an open source project. Want a proof ? Look at his amazing job on Mongoid !

The big first feature he is going to work on is the inline editing. But for now, his job is to clean the code and to build a solid tests suite. I should say I’m super astonished by his work and his efficiency.

And more than that, we are on the same page and we are pretty so sure Locomotive CMS is going to rock ! 

Stay stuned.

p.s.: By the way, thank you so much Jacques !

When Didier first approached me to work on a user interface for Locomotive, his content management system (at the time still called NoCoffeeCMS), I thought it was a great opportunity to finally design my ideal CMS interface. I’ve worked with Joomla, Wordpress, Textpattern, and Expression Engine, and none of them had that perfect mix of features, flexibility, and good design (although Wordpress and Expression Engine came pretty close).

I was inspired by the tabs of The Hit List, a Mac to-do app, and quickly came up with a first mockup, which ended up being pretty close to the final product.

We tweaked the colors and buttons some more, and came up with the idea of assigning a different color to each tab.

Around that time, we also came up with the name “Locomotive”. We liked how it related to the Rails world, and evokes something powerful enough to pull a lot of weight. I remember how I used to play Railroad Tycoon (now renamed Railroads) as a kid, and went looking for locomotive inspiration. The Golden State Locomotive was a perfect mascot: sleek, powerful, and has a beautiful retro art-deco feel.

Since I can’t draw anything more complex than a modal pop-up, the very talented Emmanuel Grard did the actual vector rendering of the locomotive. For the front-end site, we knew that we wanted something that matched the back-end’s colors and style. But I went too far in trying to keep things simple, and the result looked uninspired and dry.

Thankfully Didier wasn’t afraid to call me out on it and push me harder, and so the second version was completely different, and much more promising.

But something was still missing. The design felt flat and lacking impact, and more importantly my girlfriend didn’t like it (Dribbble might be nice, but no one beats girlfriends when it comes to giving out criticism) It was also clear that the site didn’t evoke the Ruby universe enough. It was time for a bold move.

Applying a single gradient turned out to make a huge difference, and all the other elements started falling into place. A few tweaks later, Locomotive’s home page was finally good to go. By the way, you might have noticed that the site doesn’t have any navigation. I liked the idea of the homepage being self-contained. I think it encourages people to scroll down the page, while reassuring them that they won’t need to browse through dozens of pages to find the info they need. So there you go. I encourage you to give Locomotive a try, and await your feedback on the design and general user experience.

I’d like to thank Nicholas Young who gives us the domain name locomotivecms.com.

We didn’t ask for anything, he just sent us an email and told us he wanted to help the project. 

That’s very kind to him.

Hi folks, 

It’s been a long road to launch this beta. That was really tough to stop adding new features and to be focus to release something. Yes, I had to struggle against my nature but I managed at the end !

I spent a lot of time writing a good installation guide, especially for the Heroku part. I hope it is clear enough. If it is not, feel free to send me your suggestions at info@locomotivecms.com.

Besides, I added the themes section, which is useful if you want to try Locomotive with a real example.
I just took some nice templates from different gallery templates or blog (thanks Tom by the way !) and converted them for Locomotive. I suggest you to take a look at them because you will understand how the Locomotive templates and the other modules work.
Actually, it is pretty easy to convert a html template since I have a special tool for that. I call it the Locomotive Editor (fancy name, isn’t it ?). Basically, it is based on the locomotive engine bundled in a Sinatra app but without mongodb and other stuff like the back-office for instance. The edition of templates, contents and other assets can be done with a simple text editor, Textmate in my case. Once I’m done with a theme, I simply zip the folder and import it in Locomotive.
For now, I don’t plan to open source the editor. It depends on the way I’m going to “monetize” Locomotive. Even if I’ve got several ideas, I’ve not taken a decision yet.

What are the next steps for Locomotive ?

First of all, I expect a lot from developers. I’m looking for feedbacks and even for bugs to solve !
On my side, I’m going to write tutorials. The first one will be probably about how to create a custom content and use it in a liquid template. 

You are a company and you want to use Locomotive to host a couple of websites ?

Even if you build super sexy and big apps, you always have to manage some simple websites for small clients. That’s not a problem anymore ! I’m willing to help companies which want Locomotive as their website hosting solution for their clients. Locomotive is definitely a good fit for you ! For instance, I’ve got a single Locomotive instance running on Heroku and serving 3 websites (http://www.locomotivecms.com is one of them).

I’m very excited to see how Locomotive’s going to turn out ! I’m sure it will help people a lot to build and edit websites. That’s the reason why I created it.

First of all, I would to thank all of you who sent us very kind and encouraging messages, helped us to fix issues (a lot, let’s face the truth !) or developed new features. Actually, we were not expecting such a positive wave. For instance, the Locomotive back-office has been translated in German (thanks Bernd !), French and Brazilian Portuguese (thanks Raphael !). Believe me, it is always a great moment when you see your app in another language.

More than that, some companies adopted Locomotive on a daily basis. The Frontier Group, a web design and development company, built many websites powered by our engine. The feedbacks given by 3 of their employees (Dirk, Mario and Karl) were tremendous helpful for our CMS. They did an amazing job by fixing a lot of issues and answering questions from the community. 
I also could name John, Bernd, Raphael, Benjamin for their great help. I hope actually I don’t forget someone :-) 

By the way, folks, if you built a site with Locomotive and you want to show proudly your work, send us an email, we will feature you on our blog (+ twitter as well).

Will there be a roadmap ?

I don’t think so. At first, I tried to release specific versions of the Locomotive gem. But, pretty quickly, it seemed clear to me that it does make any sense since, unfortunately, there still were bugs to be fixed the day after, making the release quickly outdated. That is mainly because Locomotive is still a young project.

Anyway, I keep up-to-date a todo list for tasks / issues / new features. Let me share the main ones with you. By the way, the order does not reflect the priority:

• documentation. [UPDATE] documentation about the liquid syntax is coming soon.
• duostack version. LocomotiveCMS should work with both Heroku and Duostack only by specifying it in the locomotive.rb config file.
• associations in the custom content types. simple at the beginning: belongs_to/has_many
• internationalization. Pages, content types, assets have a different version depending on the locale (specified in the url or the domain).
• enhancement of the inline editing module. Uploading images is not implemented for now for instance, …etc.
• a better way to install locomotive in a mono-site mode.
• dynamic image resizing. Only by using a special liquid tag, the image (images from asset collections and content types) will be resized. {{ ‘foo.png’ | transform: ‘500x400#’ | image_tag }}. Varnish + Rack.
• moving all the Locomotive models into a brand new namespace. (Locomotive::Site, Locomotive::Page, …etc). Crucial for a better integration in another Rails app.
• convert css into scss.
• integration with an existing rails app. I wish Locomotive could be used as the cms module of any Rails app.

As you can see, nothing major (except for the “Internationalization”) because I am following the same rules I apply since the beginning. Keep the core as simple / light as possible and refine / refactor as often as possible. Besides, I pay attention to the delivered code, or at least I try to.

My mojo ? The development of new features should be only driven by the need of them.

Want to contribute ?

A lot of people asked me what was the best way to contribute to the project and how they could help. My answer is quite simple. Use Locomotive for your websites for real !!! If you need a feature or if you run into a bug, fork the project, fix or implement and then submit your pull request on github.

Anyway, again, thanks to all of you who were enough patient to check Locomotive despite the bugs and saw its great potential !

What’s next ?

It seems that some people get worried about the durability of LocomotiveCMS which is, in my point of view, a very pertinent question. 
First, as I mentioned it at the beginning of the post, a lot of companies are using Locomotive meaning that you will always find someone who can help you.
Then and that’s the beauty of the open source, you are not an hostage of a product. I mean, the code is clear and can be easily modified.
Lastly, things are moving fast for Locomotive and we are going to announce some big news in the next weeks. I will talk more about it in my next post. 

choo-choo :-)

LocomotiveCMS is a very young open source project but it gets more and more users each week. More users also means that we have to deal with more work like answering questions, look into feature requests, fixing bugs of course, …etc. That’s the price of fame ! 

Unfortunately, all of these tasks take a lot of time. At the end, we spend more time on LocomotiveCMS than on our other (paid) projects which can compromise the future of our CMS.

That being said, the situation also made us think about how we were going to monetize LocomotiveCMS. We had in mind a couple of obvious ideas like providing a hosting platform for example.
In fact, we are already collaborating with a startup (bushi.do) which its activity is to who offers hosting solutions for any open source project. We’ll talk about it very soon. Believe us, it i’s going to be huge !

Since we already developed a command line tool to quickly build Locomotive websites, we came to the conclusion that it would be simpler for us, in terms of development, to sell it.
Moreover, our tool was used successfully by a couple of early adopters. Besides, it became obvious we were going to sell other tools or modules, for the reason that our philosophy on this project is to keep the core engine as simple as possible. One thing leading to another, we ended up with the modules marketplace solution.

The concept behind is quite simple. Let’s say, as a developer and LocomotiveCMS user, you miss a functionality which has a business value for you and certainly for other people / companies. No problem ! You develop it with our help (that way we validate your idea), we sell it directly from the LocomotiveCMS official website and we share the revenues. The percentage will depend on our contribution to each module’s development.

Does our modules marketplace break the spirit of the open source ? We don’t think so.
First, there is nothing preventing people to use LocomotiveCMS, the core engine remaining free of charge and we won’t force developers to sell their modules if they want them to be free.
Secondly, we do need revenues to regularly continue the development of Locomotive.
And lastly, we do like the idea to imply developers in the whole business environment.

One more thing :-) We looked for a way to sell ruby gems because all our modules will be ruby gems but we didn’t find anything.
So yes, we built our own platform named gemforsale ! For now, the marketplace functionality is not totally implemented but the basic functionalities are here.

We strongly believe that selling gems will help a lot of open source projects to generate revenues.

We are pretty excited by the way Locomotive is growing and we believe it’s going to be a major CMS soon, thanks to our users and contributors !

By the way, we’d be glad to get feedback and ideas from you.

Here is a pretty exhaustive list of what the BIG MERGE includes:

• upgrade the list of gems: Rails 3.0.9, Devise 1.3.4, Rake 0.9.2, …etc 
• roles with the CanCan gem
  note: 3 kind of roles. Administrator (they can do everything), Designer (like Administrator but applied on a single website), Author (only edit pages and contents) 
• resizing images on the fly (ticket #79)
• tinyMCE enhancements (ticket #99): 
  - the locomotive image plugin has been replaced by the locomotive media plugin which allows you to upload any kind of files
  -  fullscreen mode, very convenient to edit a long text 
• remove asset_collections
  note: the asset collections tab was confusing for users (and me too). Actually, it’s like a content type with a different kind of view in the back-office (the galery view is not implemented yet)
• use dashes instead of underscores (ticket #56):
   note: pages (slug) and contents (permalink) uses the parameterize String method.
• SEO (tickets #57 & #90):
   - index and index/ are the same page now (301 redirection)
   - add a seo_title for both the site, the page and content objects.
   - write a {% seo %} liquid tag to display the title, meta (description and keywords) tags depending on the context
• fix issue about httparty (ticket #91)
• check if custom contents are organized in a category when displaying the select box for the has_one / has_many fields
• add 2 liquid global variables in the page conext: current time and date. Dates from a custom content are now comparable
• site export (but editable_elements inside a page are not correctly handled for now)
• rake task to import a remote template
• UI tweaks, a quick list of some of them:
  - better hints for the theme asset new/edit action
  - slight modifications on forms: separator between fields, text shadow, error message redesigned, …etc
  - quick link to edit directly a model from the submenu 
• new sites picker (if the multi_sites mode is enabled and correctly set up)
• the robots.txt can be edited directly from the back-office (site settings) (ticket #57)
• 2 new languages:
  - dutch (#92)
   - spanish (#103)
• a lot of internal refactoring as well as a ton of bug corrections

Checkout the following link for the upgrade procedure:
http://www.locomotivecms.com/support/howto/upgrade 

I’d like to thank all the contributors, users and developers who reported bugs / problems or just simply suggested relevant improvements. Seriously folks, THANK YOU SO MUCH !

A very special and big thank to 2 companies. The first one, a german company (designhunger) run by Bernd Hauser, funded the has_one / has_many feature. If you are in touch with him, please thank him, he deserves it :-) 

The other one is a startup from San Francisco named Bushi.do. Sean and Kevin, the 2 owners behind this company, have been helping us so much for a couple of months now. They provide us a financial support so that we can be focused as much as possible on the CMS. On top of that, they provide us a great help for the documentation (believe me they are working hard to deliver a top notch FAQ) and they also advise us on the commercial side of LocomotiveCMS.
Working with them led, in a first time, to the update to the demo section. Before our partnership, the demo section was just a simple application with the same credentials for everyone and without the ability to edit the demo website. Now, anyone can launch as many LocomotiveCMS websites as they want and do everything possible with them !
The bushi.do people rock and I love their product ! 

To sum up things, I feel so great about LocomotiveCMS !

Great news! So many of you have been looking to connect in real time with the Locomotive team and community, we really wanted to create a centralized place for it.

So, now we have the official IRC channel #locomotivecms at irc.freenode.net! Here’s a link to chat right now: http://webchat.freenode.net/

We’ll generally have someone in there to answer questions, and we encourage you to do the same. Stop by, chat, get help, and help other Locomotive users!

See you there!

Hi everyone,

we have completely redesigned www.locomotivecms.com and we are excited to share it with you today.

The old design served us well and Sacha did an amazing job, but we felt we had to update it to make it easier to understand how LocomotiveCMS works.

LocomotiveCMS is very popular and we are very happy with all the love and excitment we feel around our CMS. And yet, we've been struggling explaining the workflow, how we stand out from the other platforms out there.

We often get asked: "What is Wagon?" (formerly the LocomotiveEditor) and "How are you different from Wordpress"?

So we've created this website to answer all these questions and help you get the most out of our amazing CMS. 

The website is not perfect yet, there is so much more we'd like to share with you (we are working on an explainer video) but we hope you like it.

And please, be brutally honest with us. Do you like the new design? What would you add? What needs to be explained more thoroughly?

We'll share updates,tips and case studies every week in this blog so please subscribe to our newsletter or follow us on Twitter.

I'm sure you are wondering who is behind the new design. Sacha again? No, not this time.

I was actually browsing Dribbble when I stumbled upon the Bugherd design and I instantly fell in love with it. So I contacted Kenny Williams and he did this amazing design for us (don't you love the halo effect on the homepage!).

Well, Bugherd has redesigned their website since then, but please, go ahead and check out Kenny's work on Dribbble.

We’d love to hear what you love about the new design. Please give us your thoughts in the comments or by email at support@locomotivecms.com.

Cheers,

Estelle

Interview by Estelle Lafforgue

Le Wattman is a digital agency founded in 2010, with a strong mission: through inspired, innovative and creative design and the use of cutting-edge technology we are able to build smart interfaces and enhance device efficiency.
With our new, unique and future-forward vision of the web, a vision based on efficiency, simplicity and our core values, we operate at all different levels on our clients' digital strategy: consulting & budgeting, creation of mobile web & extremely responsive websites, development of user-friendly mobile apps and development of specific technical tailor-made interfaces. 

HEADQUARTERS: Paris, France

PREVIOUS/ALTERNATIVE CMS USED: Wordpress / Refinery / Radiant / own CMS

EXAMPLE OF LOCOMOTIVECMS WEBSITES: http://www.anthonyramet.com / http://www.praxy.fr / 
http://artbyblazejr.com/ http://whosdeep.com/

THE PROBLEM: it was difficult to boostrap and to maintain our own CMS.  For our customer, the first issue is to be able to modify their content EFFICIENTLY.

THE SOLUTION: It's easy to propose LocomotiveCMS to our customer after a quick demo of front editing capabilities. And for our team the Wagon is a great tool for maintaining code through Git.

THE RESULTS: Happier customers and efficient coding!

THE STRATEGY: We use only Ruby language and for us choosing LocomotiveCMS is evident. First we are coding a proto w/ Wagon and providing a demo to our customers, then we improve the AD; finally, we push to the production version to let the users write their own content.

Changelog for the 2.1.0 milestone

How to upgrade ? Visit this page.

Major features:

• Search: still experimental, documentation is coming soon.
• New field types for content types: email, tags, integer and float.
• Simple field types lik input, text, email, integer and float can be unique or not.
• Pagination for content entries.
• Export in CSV of content entries.
• Liquid tag to retrieve a page variable using its handle.
• url_for liquid tag to generate links.
• Authors can create new pages.
• Major gems upgrades like for Mongoid for instance.
• API key instead of using email/password when pushing a site with Wagon.

List of all closed features/issues:

• [API] API key instead of email/password (feature)
• Deleting a model which is related to another will cause a Mongoid::Errors::DocumentNotFound in Locomotive::ContentEntriesController#edit (issue)
• ( feature request ) : Add "escape_javascript" filter to locomotive liquid (feature)
• Added specs for issue #448
• Liquid filters: stylesheeturl and javascripturl should append to path, not to URL (issue)
• Page#edit localized URL omits locale (issue)
• page.fullpath doesn't get updated when parent fullpath changes (issue)
• Failing to reorder "custom fields" on "Editing model" page (issue)
• Pages translations not falling back to english (issue)
• Bug when entering more than 10 "belongs_to" items (issue)
• Option : uniqueness of a content entry field (feature)
• Flash notice show error encode characters when translate to zh-CN (issue)
• Unable to update content type "required" attributes via back-office (issue)
• Add attributes like "defer" on Javascript tag (feature)
• Small issue for non-english sites - locale switch (feature)
• gt, lt and others not works properly for with_scope (feature)
• [feature request] tag to retrieve a page variable using its handle (feature)
• not clear how you get iso or name out of the locale object (feature, question)
• Updating some gems versions
• Important security update for Dragonfly (feature)
• Published options on all models (feature)
• Pages not updating when a snippet is updated (issue)
• Setting an existing editable element as fixed (issue)
• Locomotive API
• Enable pagination in back office for content types (feature)
• [feature request] url_for tag to generate links (feature)
• Other rails engines and catch all route. (feature)
• Old version of mongoid (feature)
• Feature request : localized templates (feature)
• Export content entries in CSV (feature)
• Add ability to backup entire site or add a 'Pull' feature to Locomotive Editor (feature, editor)
• Image upload fails (issue)
• with_scope: replace _permalink by _slug in the query (issue)
• Add JSONP Support (feature)
• Some Of The Global Variable Produce Errors, loco 2.0 (feature)
• Scss and coffee compilation within Web UI
• Editor's nav tag does not render correctly (editor)
• Model problems (feature)
• Uploading a file through the lightbox for the HABM needs a loader (feature)
• HEROKUAPIKEY (feature)
• simple text search through pages (feature)
• Project roadmap
• Authors should be able to create new pages (feature)
• Editable select and nav group 2.0
• Compile scss and coffee for 2.0
• Force SSL Testing (feature)
• Create a wrapper / generator gem 'locomotive' like the 'rails' gem (feature)
• Coffeescript support for admin assets
• liquidable robots.txt in site settings (feature)
• Support for Coffeescript / SASS (feature)
• handle coffeescript (feature, editor)
• Authentication on pages
• HTML5 Syntax (feature)
• Support multiple templatized pages in a single URL
• Multi-valued attributes in models (feature)

People who participated:

Thanks to all of you guys! Please let us know if we forgot anyone.

• did
• Papipo
• youroff
• hems
• aaronrenner
• widescape
• jasongonzales23
• jloosfelt
• kamechb
• mrrobdlon
• stunjiturner
• Manuite
• dimonzozo
• filipechagas
• gabrielnau
• alepore
• greeneca
• alexsanford
• rpechayr
• eicca
• ulitiy
• drc37
• bcardi
• septerr
• paulsponagl
• lmonfredo
• designhunger
• miskander
• pollingj
• cwoodcox
• mkempe
• alexkravets
• petrblaho
• anoras
• Cornflex
• isaac

Changelog for the 2.2.0 milestone

How to upgrade ? Check this link.

Major features

• with_scope complex conditions
• EditableShortText / EditableLongText merged into EditableText
• link_to tag for content entries
• enable simple search when choosing a belongs_to instead of select
• Site or User timezone setting 

List of all closed features/issues:

• Public submission issue (issue)
• Empty partial before Backbone init for extensions by main app
• Liquid error: undefined method `title' for nil:NilClass when using link_to feature (issue, question)
• Entry was not created permalink not translated (feature)
• Rely on external mongoid session store gem
• Nb locale fix
• #destroy_session not implemented (issue)
• Added tests for localized content entries
• Fonts management (feature)
• Rc11 : required has many cause entry creation fail (feature)
• Ability::ROLES problem when there is a local ability.rb (question)
• missing seo_title for content type in editor (issue, editor)

People who participated:

Thanks to all ! Please let us know if we forgot somebody.

• Manuite
• did
• geku
• hems
• Papipo
• joaovpmamede
• alepore
• benhutton
• Sharagoz
• widescape
• jloosfelt
• rpechayr
• youroff
• gabrielnau
• aaronrenner
• niedfelj
• dimonzozo

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras aliquam, velit eget egestas facilisis, enim diam feugiat enim, vitae lacinia erat nunc at lacus. Ut ornare elit consectetur augue ultrices ultrices. Proin ultrices, mauris non ornare rhoncus, elit ligula sagittis risus, euismod tempor est augue vitae justo. Nunc non dui nec urna cursus rutrum. Duis ante lectus, tincidunt ac commodo eget, varius et tellus. Vestibulum erat enim, mollis molestie consectetur sed, molestie eget mi. Morbi consectetur semper lectus sed lacinia. Curabitur a libero arcu, sed hendrerit orci. Sed commodo pellentesque arcu eget sagittis.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras aliquam, velit eget egestas facilisis, enim diam feugiat enim, vitae lacinia erat nunc at lacus. Ut ornare elit consectetur augue ultrices ultrices. Proin ultrices, mauris non ornare rhoncus, elit ligula sagittis risus, euismod tempor est augue vitae justo. Nunc non dui nec urna cursus rutrum. Duis ante lectus, tincidunt ac commodo eget, varius et tellus. Vestibulum erat enim, mollis molestie consectetur sed, molestie eget mi. Morbi consectetur semper lectus sed lacinia. Curabitur a libero arcu, sed hendrerit orci. Sed commodo pellentesque arcu eget sagittis.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras aliquam, velit eget egestas facilisis, enim diam feugiat enim, vitae lacinia erat nunc at lacus. Ut ornare elit consectetur augue ultrices ultrices. Proin ultrices, mauris non ornare rhoncus, elit ligula sagittis risus, euismod tempor est augue vitae justo. Nunc non dui nec urna cursus rutrum. Duis ante lectus, tincidunt ac commodo eget, varius et tellus. Vestibulum erat enim, mollis molestie consectetur sed, molestie eget mi. Morbi consectetur semper lectus sed lacinia. Curabitur a libero arcu, sed hendrerit orci. Sed commodo pellentesque arcu eget sagittis.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras aliquam, velit eget egestas facilisis, enim diam feugiat enim, vitae lacinia erat nunc at lacus. Ut ornare elit consectetur augue ultrices ultrices. Proin ultrices, mauris non ornare rhoncus, elit ligula sagittis risus, euismod tempor est augue vitae justo. Nunc non dui nec urna cursus rutrum. Duis ante lectus, tincidunt ac commodo eget, varius et tellus. Vestibulum erat enim, mollis molestie consectetur sed, molestie eget mi. Morbi consectetur semper lectus sed lacinia. Curabitur a libero arcu, sed hendrerit orci. Sed commodo pellentesque arcu eget sagittis.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras aliquam, velit eget egestas facilisis, enim diam feugiat enim, vitae lacinia erat nunc at lacus. Ut ornare elit consectetur augue ultrices ultrices. Proin ultrices, mauris non ornare rhoncus, elit ligula sagittis risus, euismod tempor est augue vitae justo. Nunc non dui nec urna cursus rutrum. Duis ante lectus, tincidunt ac commodo eget, varius et tellus. Vestibulum erat enim, mollis molestie consectetur sed, molestie eget mi. Morbi consectetur semper lectus sed lacinia. Curabitur a libero arcu, sed hendrerit orci. Sed commodo pellentesque arcu eget sagittis.

We strongly believe that selling gems will help a lot of open source projects to generate revenues.

Aliquam et dui sed lacus cursus malesuada. Ut est eros, ultrices eget vestibulum at, porttitor ullamcorper velit. Aenean consequat turpis eget odio bibendum blandit. Fusce ac turpis id magna ultricies varius. Donec a metus velit, id fermentum risus. Sed id neque eget tortor tempor laoreet ac vel lacus. Sed mollis lacus eu justo fermentum ut aliquam eros molestie. Vestibulum consectetur aliquet ipsum quis semper.

Nunc malesuada augue vitae leo malesuada sit amet viverra elit elementum. Suspendisse justo metus, dictum id lacinia non, bibendum eget nisl. Nullam vitae metus urna. Curabitur leo nibh, gravida non fringilla non, ullamcorper condimentum velit. Suspendisse nunc sapien, facilisis quis vulputate non, egestas sit amet nunc. Suspendisse potenti. Nullam a nisl urna. Sed consequat dignissim placerat. Mauris diam quam, mollis iaculis imperdiet eu, euismod vel mi. Aliquam luctus urna ac tortor imperdiet ac ornare elit luctus. Nullam gravida interdum eros nec tristique. Nulla gravida, tortor sit amet eleifend sollicitudin, tortor magna faucibus justo, in cursus arcu massa id dui. Quisque vel dui id dolor dapibus venenatis nec id nulla. Integer ut eros in nulla dapibus venenatis. Nulla vel metus arcu, consequat consectetur arcu.

Hello,

a few weeks ago, we asked everyone on our mailing list what new tutorials they'd like to see on the LocomotiveCMS documentation website.

We collected queries both from beginners as well as from advanced users and we've put up the following list together:

• What is LocomotiveCMS and why use it?
• Getting started: the ideal development workflow
• How to create a blog with LocomotiveCMS (video tutorial)
• How to use the Search feature
• Wagon command line
• Wagon File Naming Conventions
• How to customize the back office (UI)
• How to set up multi-lingual sites
• How to set up multisites
• How to use with_scope
• How to use HAML, CoffeeScript, SASS, and LESS with Wagon
• Inline Editing: How to use the Aloha Editor
• In-Depth Guide/Example Site: Adding Maps to Content Types
• How to integrate Rails Models

Some of these guides have already been written and we are looking forward to sharing them with you.
We really want to improve the documentation website beforehand though and the way information is oganized so we'll have to keep you waiting a little bit longer. But make sure to follow us on twitter as we'll notify our followers each time a new guide is published.

If you have any other suggestions or guides that you'd like to add to the list, please let us know.