Now we can have something write our code to help us save time writing more code.
You should add inline comments to the tasks that explain what is happening and why so when people new to Gulp need to modify or extend their generated tasks, they can reference what's already been generated for them.
Also, I think it would be cool to add some functionality to save what options you had inputted via a query string so users can come back and add another option if needed. Modernizr uses a similar technique when you create a custom build of the library (except they use a hash URL, not a query string).
Two excellent suggestions. Already have the query string functionality on my todo list and I'm adding the inline comment suggestion right now.
Thanks, Alex! Keep 'em coming!
Love gulp, love this!
This is a cool little tool. Thanks for building this.
I wrote an article a few weeks ago called "Using Gulp in Your Web Design Workflow" that outlined what Gulp is and how you can use it to automate a number of tasks in your web design workflow. It got a lot of great feedback and it inspired me to build a tool that makes getting started with Gulp even easier. The goal was to build something that requires minimal input and minimal effort to execute.
This is very much a work in progress, so please let me know if you encounter bugs or have any general feedback on how I can improve it.
You should add some tweet/share buttons to the site somewhere :) Make it easily to post out! Awesome work!
Thanks, Zach! Love the idea. Also have a share button on the todo list that let's people link specific configurations.
Nice, I've used headstart.io which has a little bit more hand-holding. This might be a good transition from it!
Headstart looks really interesting -- very configurable and, yes, very well documented. It seems a little overwhelming at first though. I wouldn't mind looking to find a middle ground here; something that provides ease of use but still allows for the configuration people are looking for.
Thanks for the link!
I was thinking about writing something like this, glad somebody did it for me ;)
Have you looked into taking this underlying process and creating an API out of it? Recently I was learning how Yeoman generators work, and they created a tool that streamlines the modifying of Gruntfiles. A similar tool to programmatically generate and modify Gulp tasks could have some interesting uses.
Yay! Thanks, Geoff.
Definitely a good idea. There is a similar existing solution that works with Yeoman (https://github.com/yeoman/generator-gulp-webapp) and actually someone has already built something similar to what you're talking about (http://slushjs.github.io/generators/#/). I don't know are both quite "perfect" though -- finding that balance between ease of use and providing too many options is difficult. I'll be iterating on Quench, so keep submitting feedback if you think of it. This is a great start.
More what I'm talking about is a library that lets you modify a Gulpfile without using a templating language. (Here's the library Yeoman uses for Grunt.) Slush is interesting, but when it was released I couldn't really figure out what it does different from Yeoman, other than be built with Gulp. (And Yeoman doesn't actually use Grunt for anything from what I can tell, it's just that most generators happen to use Grunt.)
It is funny though, having conversations about abstracting something that's already meant to be an abstraction. Because y'know, web development. ;)
Yo! I heard you like automation, so I wrote a tool so you can automate while you automate!
Seriously though, this is getting a bit ridiculous!