Gulp for bigger projects
Knowing how to use Gulp is one thing, but how do you set it up in such a way that you don't end up with some 7000 line monster gulpfile that no one in your team likes using because it crashes their PHPStorm on opening?
There's all kinds of benefits from separating your gulp tasks into individual files:
- definite separation of concerns
- easily find any specific task at a glance
- far easier to selectively re-use useful tasks per project
But there is one downside.
It does look a little scary, and that makes it initially harder to understand at first.
Now back to the good news.
This is nothing we haven't already learned.
Instead, this is an optional step that may or may not suit your needs.
By the end of this video you will have gained an understand of one way to go about managing, maintaining, and organising Gulp for larger projects. You may have a better way, and that's great if you do - and please do share optimisations or improvements.