hey josh,
i was just doing one of my periodic scans of the state of things in the 'spa' build space, and i came across warlock.
i am currently using a grunt setup influenced by ngbp, deviating in that it uses sass, jade and a local express server for
serving up a 'mock' version of what would be served up by rails in a deployed environment.
so, i was going to start up a little spare-time exercise to learn type-script, and i figured it was also a good time to take stock
of the state of things in the 'spa' build space, so i have been reading up a bit on gulp, brunch and mimosa.
since i'm still relatively inexperienced in front-end dev, i was leaning towards something that had some pre-defined convention to it,
so after some review i decided something like brunch or mimosa would be a better fit for my purpose.
brunch is more popular than mimosa, but of one of the things i didn't like is that there are so many skeletons to choose from,
that i quickly became overwhelmed attempting to decide which one to use.
also, perhaps more importantly, i only found one that supported the modularity of ngbp, and i couldn't get live-reload to work
(not sure if that was due to the skeleton or brunch itself tho)
i liked mimosa in that it prompts for preferred stack elements at project creation time (e.g. coffeescript, jade, etc),
and it's live-reload feature worked out-of-the-box, but it's default setup didn't have the ngbp modularity goodness.
so winding up, i really like the promise of warlock because of the cool convention of it all and the modularity goodness.
as i said, i'm kind of an intermediate front-end guy, but i'd be happy to help out if you have any tasks that might not require
expert level experience. maybe i could try my hand at a spell or two to chip away at your short list if you have one?
regards,
tony.