Should you wish to roll your own Material Design Lite custom build that works with WSK, try our MDL Sass guide.

ES2015 via Babel

We also have added optional ES2015/ES6 support using Babel which you can enable by removing the line "only": "gulpfile.babel.js", in the .babelrc file.Thanks to Babel, the ES2015 source code will be automatically transpiled to ES5 for wide browser support.

We've also ES2015'ified our Gulpfile:

ESLint code-linting

We now use ESLint for code linting and code-styling. ESLint is a pluggable and configurable linter tool for identifying and reporting on issues in your JavaScript. We’ve setup ESLint to use our brand new ESLint configuration for the Google JavaScript style guide, which you are free to customise further.

// Lint JavaScript
gulp.task('lint', () =>
  gulp.src('app/scripts/**/*.js')
    .pipe($.eslint())
    .pipe($.eslint.format())
    .pipe($.if(!browserSync.active, $.eslint.failOnError()))
);

Service Worker Pre-caching

Offline support (basically, your site working when a network connection isn't available) is now enabled out of the box thanks to Service Workers and sw-precache. They work by intercepting network requests made from a page, returning a response retrieved from the network. Alternatively they can retrieve from a local cache, or even constructed programmatically. This allows it to be used for intelligent offline caching of your site.

Progressive Web App Support

“Progressive Web Apps” is an umbrella term for modern, performant web apps that cleverly take advantage of technologies like web manifest, service worker, responsive web design, etc. to provide a top-tier experience on mobile.

Web Starter Kit has:

• Offline support via Service Worker
• Web Application manifest
• Splash screen support on mobile

Deployment

If you would like to deploy your WSK project to Firebase, Google App Engine or another provider, guides are available to help you get your site pushed.

Lowering the entry-level for beginners

We understand that WSK comes with a lot of tooling out of the box and this can sometimes feel a little overwhelming for beginners. This is why in WSK 0.6.0, you can get open up the app directory and serve it up using a Python server, WAMP or any local server setup already on your system. Run an npm install when you feel you're ready for the more powerful BrowserSync setup and build-time performance optimisation tools WSK includes.

Lots of bug fixes

Last but not least, we have added improvements to our build process, fixing a number of in minification, sourcemap generation and much more. Whether you use WSK or not, the Gulpfile remains an excellent reference for how to craft a build process with performance optimisation in mind.

Happy coding!

PS: If you're happy using Polymer, we also maintain Polymer Starter Kit which includes a similar set of features optimised for working with Web Components.