Gulp support

[bmuenzenmeyer]

Remaining todo to ship this:

• Update gulpfile to omit scss where possible as a default
• Revert project back to grunt-first
• Update readme with browsersync
• Update readme installation instructions to help users wanting to init with gulp. Mention Windows caveat
• Update readme to help users switch to gulp
• Create upgrade instructions
• Create known issue section in readme for the other device page follow problems using the menu.
• Changelog
• Make sure gulp files are properly cited as deriving form oscar-g's work
• Create ticket for small optimization to better target grunt watches more efficiently
• Remove sass from package jsons, instead include directions to include and turn on

[oscar-g]

I've started on this here: https://github.com/oscar-g/patternlab-node/tree/dev-gulp
I'm almost done...There is still jshint, watch, and sass tasks to configure.

[yuvilio]

That's great @oscar-g. Feel free to ping whenever you need testers to generate with it.

[bmuenzenmeyer]

@oscar-g this is great! I am excited to dig in and learn more about gulp soon. Thank you so much for taking the reins on this. I'd love to see the pl-node repo structured in such a way that it supports node,grunt and gulp versions.

Any thoughts?

[ivanmayes]

@bmuenzenmeyer, might be useful to pull in a library like https://github.com/chjj/blessed to let people configure for vanilla, grunt, or gulp and then add the processes in / node modules based on the selection. http://yeoman.io would be another option to allow people to select their preference when they build out the project.

[oscar-g]

@yuvilio - You're welcome, I'll be working on it today.

@bmuenzenmeyer - Another way of doing that would be with a Yeoman generator. For example, check out Keystone JS, and it's Yeoman generator: https://github.com/keystonejs/generator-keystone. That generator let's you choose different build step systems and template engines for their CMS app.

@ivanmayes - I've never seen that library, I'll check it out!

edit:
Okay, it's ready! The task names and their structures are a bit different than the grunt version, but it's still pretty simple. I'm thinking that if we end up using yeoman, or something similar, we may have to move some tasks from gulpfile.js to builder/gulp-patternlab.js.

[oscar-g]

Has anybody gotten the chance to work with the gulp branch in their specific environment?

• Thanks!

[ivanmayes]

We have a project coming up that we will be trying to integrate the gulp version into in the next month. Our boilerplate has the vanilla version at the moment, but the rest of our boilerplate uses gulp.

[bmuenzenmeyer]

Hi @oscar-g and all,

I briefly looked at this the other day but did not run it.

I think in the short term I would accept some pull requests into the dev branch, and then would address the grunt/gulp/vanilla versions in the readme.

In the midterm, I would break out the versions into specifc repos that reference the pure node version, similar to https://github.com/kangax/html-minifier.

The final step(s) then would be npm/bower/yeoman etc.

Does this make sense? Looking for some feedback on how best to structure the project to be clear, maintainable, and approachable to newcomers and veterans alike.

Thanks for the continued support - I have some things to finish up this month but then plan on further development.

[bmuenzenmeyer]

I haven't heard any response to my above comment - but have added some notes to the readme to address the gulp version.