You can find the completed demo in the my twig.js github project. The following are my thoughts from the experience and some instructions for setting up a project using Backbone.js and BravoJS.
You have to do some work to use Backbone as a CommonJS Modules/2.0 Module
Currently, backbone and underscore have Modules/1.1 style exports for use in node.js (or other Modules/1.1 environments). This makes it easy to adapt them to support Modules/2.0 by simply wrapping the js files with a
modules.declare call. This would be very easy to automate with a build script for your application.
MVC on the client is not MVC on the server
It's worth making the point that you don't have to do MVC on the front-end the same way as you do it no the backend. Because you don't have to serve different content types (JSON, HTML) from the same MVC you can take more liberties with your design. Also, because of the way Backbone lets you bind to events from the view, it makes it very convenient to write your control logic in the Backbone.View and handle the view rendering with a template.
A good templating engine makes your life much easier
Here's an example of the TweetView Backbone.View and template: