drumbeat build file requirements

gistfile1.txt

Cases I've been studying:

https://github.com/sbook/jingo-minify
https://github.com/jsocol/jingo-minify

What I want to have:

- serving the assets either has to modify the file name or move them into a sub-folder. I like the idea of sub-folders but not sure if that's hacky or not, I don't really want to munge the file names. Query strings aren't great as not all browsers cache a file with a query string. The sbook version hacks the file names.
- store build data inside of a YAML file - should this include file by file information or just subset by subset, eg css or js?? File by file would provide more control but would that be a bit too much of a performance hit at runtime. To be fair I can't quite grasp what either build script is doing and having that explained might provide helpful.
- parse CSS files to include version-ed file references in there
- should probably put in support for .less files (though I will not be using .less ;))
- will need the current build data thrown through to the front-end for loading JS assets

I should also probably fork an existing implementation opposed to writing my own file - admit that was a daft idea to do.