maccman/spine — Issue #178: Hem Features/Configs
Author: davidkaneda
Created: 2012-01-08 21:23:27+00:00
State: open

I'm slowly getting used to Hem and love it, especially as a means to embed the Eco templates. Would be great if we could get some extra config options though... While I appreciate the "convention over config" mentality, a few more options would go a long way in being able to bring Spine apps into other workflows (like the excellent HTML5 boilerplate...):

* Ability to explicitly set output directory (instead of public/) for CSS/JS. Lots of people don't like these things sitting next to each other, and there's currently no other way.
* Ability to simply disable CSS compression... I use Sass/Compass instead of Stylus (though I like the idea of keeping everything in Node, Sass is simply too powerful for now).

To achieve the workflow I want, I currently have a stub index.styl in my css folder, and have my public folder set to js/ — which includes an empty application.css. Tolerable, but a little annoying.

Also, side note: Would be great to know if the items Spine includes by default are required, ie. es5-shimify and json2ify. What do these add, are they necessary, etc?