Into the cloud with Rails 4
The asset pipeline offers a great way to organize assets, by filetype or by directory (/lib, /vendor). I divided my JS assets into various scripts, specifying those which as to be loaded at some specific times (eg 'domready') or for specific pages.
Most of my work on Rails goes on the back office part of this website, with the implementation of User and Post models, handled by the adequate controllers. Login mechanisms, security layers and session management have been important parts of this development. Post management implies creation, update or deletion, depending on user privileges. I developed a DraftPost model, which acts as an interface for Post's write access, storing modifications until the administrator validates them for publication.
HAML naturally comes as the most appropriate templating engine as it offers simplicity for views' editing (except for heavily nested and content oriented markup as noted by Chris Eppstein). Besides its simplicity, HAML fits with Scss files, by mirroring elements' ids or classes.
Accustomed to classic web hosting (all in one hosting plan, no scalability), 47tibo.com allowed me to dive into cloud architecture. From a developer point of view, Heroku (and others PaaS) are perfect tools, Git oriented, totally scalable and versionable. Along with Heroku comes Amazon S3 for a handy management of images assets, especially when dealing with responsive images, which implies multiple instances of the same image.