Best practice: workflow with gulp.js (or grunt.js)?
Permalink
Hi, just discovered gulp and I think it's a nice tool for building templates with automatic SCSS to CSS compiling and browser live reload, when you change files... and I'm sure there are much more goodies.
But what's the best practise when we want to build a package?
Where should we place the gulpfile.js (gruntfile.js) and the package.json? When we place these in the packages/my-package/themes/my-theme folder there are a lot of files. When work is done, we don't like to manually select the files, which must be deployed...
Could someone give us some advice with this?
Thanks.
But what's the best practise when we want to build a package?
Where should we place the gulpfile.js (gruntfile.js) and the package.json? When we place these in the packages/my-package/themes/my-theme folder there are a lot of files. When work is done, we don't like to manually select the files, which must be deployed...
Could someone give us some advice with this?
Thanks.