Skip to content
codersquid edited this page Mar 19, 2013 · 7 revisions

Templating Specs
Use Cases

  • provide templates to users for dynamic surveys whose data can be attached to registrations
  • allow users to create their own registration templates
  • allow users to add metadata to their project components
  • easily allow for models to be populated using json
Frameworks should be
  • logic-full
  • well-maintained/active community
  • easy to learn
  • relatively lightweight
  • customizable/easy to extend
Current Framework

Ember.js

Current Screenshots

Chosen Framework

Knockout.js highly recommended, haven't finished reviewing all options though

Reviewed frameworks

  • framework name
    • pros
    • cons
    • notes
  • jade
    • pros
      • good documentation
      • good community, maybe not as active as knockout.js?
      • mixins
      • logic
    • cons
  • knockout.js
    • pros
      • uses logic
      • really well documented, seems intuitive and customizable
      • active community: multiple posts per day on forums
    • cons
      • nothing, this is the platonic ideal of javascript frameworks
    • notes
      • just the templating/data-binding?
  • javascriptmvc
    • pros
      • good documentation
    • cons
    • notes
  • embeddedjs
    • pros
      • nice set of view helpers to build on
    • cons
      • sparse documentation
      • community not very active: only 27 issues in tracker, no mailing list activity since 2012 (and most in 2009/2010)
organize these Commentary

Good post from 2011 from linked in compares a lot of different frameworks. The client-side templating throwdown: mustache, handlebars, dust.js, and more. They ended up choosing dust.js.

Clone this wiki locally