Spring 2015 - Submission 8

[mcwhittemore]

Build assets with "static-pipeline" framework and original libraries, not gulp/grunt plugins

Abstract

Based on https://github.com/daiweilu/StaticPipeline

• Build tools and task runners like Gulp and Grunt all depend on their plugins. Plugins prevents you from using the real power of original assets processing tools, e.g. node-sass or browserify. Why bother learning browserify plugin instead of the browserify itself?
• For static assets to bust browser cache, we often append a hash to the asset's url. The process of hashing assets then render template with hashed url is hard to maintain and inflexible.
• Static Pipeline is a framework with which you can use whatever processor you want. It will also save each hash assets url. So you can use them with template helper to provide correct assets' urls.

  JavaScript outside of the browser

Not browser-based: My content is centered around JavaScript executing outside of a web browser.

Will you be present in Washington, DC?

I will be in Washington, DC while presenting.

Prerequisites

• Know concept of assets pre-processor, e.g. SASS, Browserify
• Heard or used grunt / gulp before

  Additional Information

  Code of Conduct

I have read, understand, and agree to follow the Node.DC Code of Conduct.

[mcwhittemore]

This is about what one can write in any programing language and I'm not sure really covers node past what lang/engine was used to run the code.

[JuanCaicedo]

I think that the idea of building a static pipeline could be applied to any application, but since it's specifically an alternative to using grunt or gulp, I think that it could be interesting to a lot of node people. I think the idea of moving away from depending on plugins to get the job done is cool, and I know it's the reason a lot of people have moved to using npm scripts. I'm all for it!

(side note, the repo is written in node, but should the link have been removed for the submission?)