feedhenry/fh-studio — Issue #27: Migrate away from Jade as Express's template language
Author: cianclarke
Created: 2012-02-01 16:09:29+00:00
State: open

At present, Jade drives the key parts of index.html when a user first hits the app on 0.0.0.0:3000/ - this renders an outline HTML page, and on the client side dust then renders what's left.
There are three routes for this task, listed in order of preference:

1) Have the very first app have Dust in Express.js (nodecode) render the very first page using res.render(), returning the full HTML required for the page load. This means first the very first time a user loads the page, no client-side templating takes place.
2) Have Express.js serve up the contents of layout.jade as it exists at the moment, ported to dust & using the dust engine.
3) Have Express.js serve up static HTML with no templating for the boilerplate instead of jade