To use this theme's dev tools, you will need to have Node and Gulp installed.
If you don't have Node installed on your machine, head to its official site and choose an appropriate installation for your system.
This will install Gulp CLI. If you have Gulp CLI already, you can skip this step.
$ npm install --global gulp-cli
This will install dependencies from theme's package.json file.
$ npm install
This will run a default development task from theme's Gulpfile. You're all set.
$ gulp
Running gulp in the theme's folder will compile the sources to dist then start a local Browsersync instance on port 3000 to serve and refresh your pages as you edit.
The default Gulp task will run following subtasks:
.html files are copied from pages to dist. Only newer files are copied during the development later on.3000 served from dist, defaults to index.html.package.json dependenciescopy in the gulpfile.js. )After running all these subtasks, there is a watcher set for changes in the HTML, SCSS and static asset files. This means, every time you will edit a .html, .scss file or add a new file to e.g. img folder, it will be automatically also compiled/copied into dist folder and the BrowserSync will automatically reload your localhost page(s) in your browser.
Running gulp build in the theme's folder will clean dist folder and then compile the sources into it.
The build Gulp task will run following subtasks:
dist folder.html files are copied from pages to dist. Only newer files are copied.package.json dependenciesstyle.default.scss into style.default.css and style.default.min.css. Vendor prefixing is done by the gulp-autoprefixer based on the setting in package.json (last 2 versions). For the minified version, also the sourcemap file is generated.copy in the gulpfile.jsAfter running all these subtasks, there is a watcher set for changes in the HTML, SCSS and static asset files.
Your cart is empty
