Front - and backend workflow optimization with Grunt

With the growing speed and complexity of the frontend development, new standards arise every day. Each developer picks up his own preferred standards and tools, but that will lead to a maintenance hell. So, how can we get the whole team (frontend and backend) on the same page for the frontend part of your web application?

What I will present is a opinionated view on how a frontend theme/webapp workflow/automation should look like in a multi-discipline team.

Example of some of the Grunt setups:

• angularjs app as drupal module
• subtheming with sass
• no ruby frontend development
• uglifying your js on the fly
• livereload without paying for the app.
• ...

Do following words sound familiar?

• ruby dependency hell
• lost css after compile
• gazzilion js plugins loaded
• subtheme inception

Then come to my session

As extra I will give some love for the picture element and the picture/breakpoint module.