Front-end paradigms are shifting fast, and among the trends singled out are task automation, painless dependency management, and quicker testing. Front-end ops, a term promulgated by Alex Sexton, deals with the synthesis of all of these responsibilities and others that front-end developers today face. We'll talk about a variety of different options available for FEDs to work efficiently and iteratively, such as Yeoman, Grunt, Gulp, Bower, and other lesser-known projects.
Here's what we'll cover:
- Why ops? Automation generates consistency
- Why front-end ops? Roles, rationales, workflow
- Getting started: Scaffolding and setup
- Automation: Grunt and Gulp
- Linting: Coding standards
- CSS: Preprocessing and aggregation
- CSS regressions
- Testing rendering engines and devices (GhostLab)
- Performance testing
- Developer tools for debugging
This session assumes some familiarity with the command line.
Preston So has designed websites since 2001 and built them in Drupal since 2007. He is a Software Engineer at Time Inc. and also co-founded the Southern Colorado User Group. Since 2008, Preston has spoken at conferences and camps across the U.S. and on two continents (most recently DrupalCon Amsterdam 2014 and DrupalCon Portland 2013) on topics such as design, theming, usability, responsive design, and cutting-edge code.