Multiple and Alternate Templating Engines

[anithri]

@Drulac opened #134 to replace EJS with template-literal . Which is an idea I quite like, though I'm open to other opinions.

But what about allowing the ability for multiple template engines? If we moved the template processing from src/models/file-info.js into the (src/models/blueprint.js)[https://github.com/SpencerCDixon/redux-cli/blob/master/src/models/blueprint.js]?

We could provide template-literal (or ejs) as the default processor, if no other processors are defined. But allow specific file types to be processed by a specific engine, and for the entire rendering process to be redefined.

// willfully ignoring pomises for brevity
import postcss from 'somewhere';
import haml from 'haml';
const postCSS = postcss(['autoprefixer','cssnext']);
module.exports = {
  // ...
  engines: { 
    css: (contents, context) => {
      return processor(contents, context, options);
    }
  }
  preRender: () => (console.log('starting'));
  postRender: () => (console.log('done'));
};