Mustache Layouts and Templates
So I had the opportunity to work with Disney on a small project spoonful.com. Two points that needed to be brought up about this project. One being mustache layouts. It's a system setup for template's on all programming platforms that includes languages outside of the the web development platform. Also, meta-tables were used and needed to be reused for the new platform ...
This was an interesting position because with relational tables, it makes things interesting with pulling records from a database because it's pulling from several tables instead of a minimal amount of tables. There were a few issues derived from this setup. 1) Easiest way to pull records from the current layout 2) Safest way to import current records into a new database 3) Keeping the information from being unrecognized on the new platform.
Now with mustache layouts, there were some easier solutions to keep bugs off the screen and kept in the back-end. Mustache allows a front end developer to pull data and display data similar to Perl template-toolkit or twig-layouts in Symfony2. There is no need to really touch the back-end code for creating the data-structures. This allows for the frontend developer to focus just on the front end coding and nothing else. Creating instances for null sets is a breeze with if statements, and pulling information from arrays, objects, etc. is easier than ... cake ... php :p
So overall, this system was an easy to get use to, and we were also able to create a few automated templating systems in the process (think, pulling variables from an api call, and having those variables available to drop into a pre-created template).
Click here to play around with mustache and see how easy logic-less templates can make your life.