evolved-theme | simple pair of parent and child themes | Style Language library

To auto install Evolved use our Yeoman generator.
To manually install Evolved either clone this repo or use the download button to save a zipped copy for yourself. Copy the contents of the root directory to your project's root directory (excluding the grunt and gulp directories) and the two theme folders to your project's themes directory (you may want to copy the .gitignore and .editorconfig to your project's root as well).
For Grunt, copy the contents of the grunt directory to your project's root directory. Open the Gruntfile.js and edit the THEMES_DIR constant to match the location of your project's themes directory.
For Gulp, copy the contents of the gulp directory to your project's root directory. Open the gulpfile.js and edit the _theme_dir variable to match the location of your project's themes directory.
To avoid version issues Node and Bower install project dependencies locally. But don't worry, they're only used for building your assets, you don't need to track them in git or include them in your production environment. Install your build tool and all of it's plugins needed for concatonation, minification, image compression, js and sass compilation, and the necessary components for live reload (these are declared in package.json). Finally install your theme dependencies like js libraries, Bourbon, and Neat (these are declared in bower.json).
If you don't have Sass installed on your machine you'll need to install that next.
Grunt is a great build tool and we've set it up so that you can concentrate on building your theme instead of optimizing how it's delivered.
Gulp is also a great build tool and we've set it up so that you can concentrate on building your theme instead of optimizing how it's delivered. At it's core Gulp is extremely powerful, but most of the time we're only going to be utilizing it for a few standard tasks. To start our new project we need to run the build task with the --dev flag. When running our project locally we want to build and concatonate our assets but not minify them. This task creates a dev directory and runs all the tasks required to build the assets. After our dev directory is created, we can run the watch task with the --dev flag to set Gulp to automatically build the dev assets and reload the browser when necessary with LiveReload. This task builds our production assets concatonating and minifying all the necessary files. These are the files used in staging and production environments. Although watch, build should get you through 90% of your workflow there are other tasks (and subtasks) you can run in the current Gulp setup. Each of these tasks (except for images) can be run with the --dev flag appended to them to create expanded files in the dev directory. Will build the styles in the dev directory for running the local site. For further reading on Gulp, checkout these posts.
Getting Started with Gulp - http://markgoodyear.com/2014/01/getting-started-with-gulp/