Define Recipe Scope

[cesutherland]

Define the desired scope of recipes. Eg. for styles, do we want a single css recipe which supports less, sass, stylus etc. transformations or individual recipes for each?

Implications:

• how many recipes we have
• how big each recipe is
• task composition for several pre-processors resulting in a single file (eg. less + stylus -> css)

This applies to source tasks (css, js, templates...).

[cesutherland]

We might take a hint from browserify which lets users choose their own transformations, but configure them declaratively using what is installed. See https://github.com/substack/node-browserify#browserifytransform