Build system feature requests

[stoff]

We're considering a rewrite of the build system. We'd love feedback on how the current system is working for you, as well as feature requests for things that you'd like to see in future versions.

Proposed direction is to stick with Gulp, move away from the "Phoenix tasks" system (so "task" will truly mean "Gulp task") and allow multiple concurrent destinations for compiled code.

Anything you'd like to add?

[ajmueller]

I'd love to see Browser Sync replace LiveReload and Icon Font replace Icomoon. They were things I had seen/had on my wish list in my head before I left (oops @elseloop there were a couple I didn't get into Github).

[jbascue]

Support for Critical CSS is going to increase and it makes a lot of sense for the more complex projects we tend to do.

• http://www.smashingmagazine.com/2015/08/understanding-critical-css/
• https://developers.google.com/speed/pagespeed/service/PrioritizeCriticalCss
• https://github.com/filamentgroup/criticalCSS

[stoff]

@mschwa commented in email, with regards to production system integration:
As a starting point, this article may provide some insight for .Net integration…

http://www.hanselman.com/blog/IntroducingGulpGruntBowerAndNpmSupportForVisualStudio.aspx

If we already have a bower package for Phoenix then this would be the way to go. I haven’t done too much with integrating front-end packages with .Net projects but I would definitely be willing to join in on a general meeting about it and provide as much insight as I can.