The Why and How of Front End Architecture

Front-end web development is evolving fast and selecting the right tools to use and when to use them is key to building successful solutions. Knowing why you might incorporate new techniques and what's a good fit for your needs can be challenging with so many choice available, whilst balancing client needs, team efficiency and code quality.

Learn from our successes and failures at architecting the front-end for projects like MSNBC, Bravo TV, Oxygen, and Highlights for Children. In this session we'll be covering the four major areas of front-end architecture:

We'll be talking about when and why you might use tools like Sass, Grunt, Gulp, Bower, Node/NPM, linters, Bootstrap etc, but without getting into the weeds of their specific implementations.

• File organisation and naming conventions
  • Make life easier when working in teams, including on-boarding new developers, as well as preventing spaghetti code.
• Build tools
  • Which tools should you choose for automating and improving your project workflow?
• Dependency Management
  • Choosing a package manager.
  • Keeping your external dependencies out of your repositories and keeping track of their versions / origins.
• Testing
  • Ensure your code is consistent and automate checks to help catch problems before they make it to production.