Ember's declarative templates allow components and pages to be described using familiar Handlebars syntax. We'll start with regular HTML and extend the vocabulary we can use in templates by using helpers and template-only components.

Components are modular and reusable chunks of UI that can be composed together to build rich web experiences while keeping complexity under control. We'll explore how components have a well-defined contract with the outside world, how the tracked decorator can be used to keep your data and DOM in sync, how to handle user interactions like clicks and form submissions, and how to write quick and effective tests to ensure things work as they should.

Services are Ember's primary tool for sharing state and behavior across many concerns in an application. We'll build a service for authentication state, and demonstrate how we can use Ember's dependency injection system to safely "stub" it in tests.

Ember's routing layer provides some powerful primitives for making sure our app is URL-driven. We'll build up a mental model for Ember's hierarchy of routes and transitions between them, and quickly move on to more advanced topics like redirecting users and preventing "logged out" users from entering certain parts of the app.

The Container/Presentational Component architecture pattern separates the world into components that either "do things" or "look like things". We'll look at how this pattern leads to code that's very easy to test, and use it to implement several features in our app that involve state and concurrency.

Making a blazing-fast ember app is easier than ever. We'll tap into the power of Ember's rich addon ecosystem to add a service worker to our app, allowing it to work offline, and fastboot for a fast server-rendered initial page load. In the end, we'll have a 0.2 page load time on desktop class browsers, and 0.7s over a 3G network connection on mid-range mobile devices!