This project is our template for Front End Development. It provides functionality to for continuous development using Grunt. It's packed full of features for our particular workflow that will hopefully help you too!

There are a number of NPM global packages needed to build the project:

$ npm install -g grunt-cli
$ npm install -g jspm

Once installed, gather your dependencies via:

$ npm install
$ jspm install

This boilerplate is structured around several nodejs tools, which aim to reduce repetitive dev tasks and improve page load times of your final product by using concatenation, minification and image compression by default. It will also give you auto-prefixing on every save of your CSS and allow livereload of the page whenever you save in your editor.

Introduce a build process to easily deliver linted, concatenated, minified CSS and JavaScript files. Also compress your images to further reduce your page load times.

A Package Manage that can install from multiple sources: NPM, GitHub or any url. JSPM comes with System.js by default, which is a polyfill for the upcoming System object in JavaScript. It also comes with Babel which allows for ES6 and above features to be transpiled into ES5 on the fly. This is still pretty experimental stuff so test it thoroughly if you use any ES6+ features.

JSPM also includes a module compiler that supports AMD, CommonJS and a mix of both to compile the app down into one file. Previously we used Require.js to do this, as Require is used the AMD model this is also supported.

NPM should only be used for installing development packages, JSPM should be used if you need any JS to run on the website (jQuery etc).

Builds of the website will end up, in /build/dev/ and /build/dist/. The dev task and dist uploads will target here.

Grunt task configuration files are kept in here, alter them to suit your needs. Ones worth noting:

• project.js: main project config file, each option's usage is documented.
• path.js: used by the build process, shouldn't need to change any of this as it is customized via project.js.

This is where all code you write/edit lives. If your project.js mode is set to "webdev", the directory is actually /src/HTML/ so the umbraco build can sit along side it. During a build of the project, most items are copied by default into the /assets/ folder. This can be configured in the /config/package.js.

• js/: JSPM will target js/app.js and compile a single file from your app.
• sass/: Sass files are passed through to PostCSS. Our configuration used libsass to compile to CSS then Autoprefixer to give vendor prefixes.
• assets/: this is indended for static assets, i.e.: images, fonts and other media.

Custom grunt tasks. Your own grunt tasks can be added here.

This is your project's management file, all devtime and runtime dependencies are defined in here. To install all of these you just need to issue a "npm install" command from the root of the project.

All Epiphany grunt tasks are defined in Gruntfile.js and prefixed with [EP]. To see all available grunt tasks run:

$ grunt --help

The Grunt Boilerplate serves as a build tool that will also host the website for you locally during development. To build your project and start the continuous development setup run:

grunt dev

This will build your project and then watch for any changes and do those individually.

You should write all your CSS in src/sass/screen.scss. If you've not used SASS before, don't worry, just write normal CSS and you'll be fine.

Grunt generates an autoprefixed screen.css file every time screen.scss is saved. The browser will automatically inject the updated CSS without a page reload on save.

Your JavaScript code should be written using the AMD or CommonJS pattern with files being saved to the js/app folder. All vendor scripts should be installed with JSPM as they will be included automatically in your compiled JS app.

During development System.js will load your scripts asynchronously from the js/app.js entry point file.

Changes to any file in /src/ will trigger a hard reset in the browser, with the exception of Sass files, which trigger a soft-css reload.

You can trigger the dev and dist build process seperatly by eith of the following:

$ grunt build     # builds /build/dist/
$ grunt build-dev # builds /build/dev/

Each time a build task is ran the existing directory is deleted before the build starts.

When your project is finished and you want to package everything up to send to the client, you should run the following grunt command.

grunt live

This first performs grunt build then bumps your major package version number. Your CSS and JavaScripts will be concatenated and minified (we still keep Modernizr seperate as we want that to load before the body). It will also optimise all your images by compressing pngs and gifs. It will add the social media scripts for Facebook, Twitter and Google Plus One at the foot of the page, and Google Analytics code at the top (you can remove the social scripts include if they are not needed).

N.B. You will need to manually enter the Analytics ID in src/HTML/_components/analytics.html.

The /build/dist/ folder can then be zipped and sent over to the client.