Skip to content


Repository files navigation

EmberFest 2018 Schedule

Adapted for EmberFest from


This tech demo is brought to you via the EmberFest sponsorship from 201 Created. Like this demo project and want to explore these cutting edge features with your own codebase? 201 Created has worked on dozens of apps with Fortune 50 companies and Y-combinator startups. Visit or email to talk with us.


  • Progressive Web App

    • Perfect 💯 Lighthouse score
    • Save to mobile home screen for fullscreen app experience
    • Offline cache fallback via service worker
  • Module Unification File Layout

    • File system migrated with ember-module-migrator
    • Review the project's file structure organized within src directory rather than app
    • Uses local component lookup (components found in context-aware -component directories)
  • Fastboot Rehydration

    What is Rehydration?

    The rehydration feature means that the Glimmer VM can take a DOM tree created using Server Side Rendering (SSR) and use it as the starting point for the append pass. This reuses the rendering work already done on the server, allowing Ember applications to start with the existing DOM rather than throwing it away and generating it all over again client-side.

  • ES5 Getters

    In this application we are running a Canary build of Ember which will eventually become 3.2. In 3.2 of Ember.js es5 getters are automatically installed for computed properties onto the Object prototype. So you can use this.myComputedProperty without reaching for the get helper

  • No jQuery!


You will need the following things properly installed on your computer.


  • git clone this repository
  • cd emberfest-schedule-2018
  • yarn install

Running / Development

Code Generators

Make use of the many generators for code, try ember help generate for more details

Running Tests

  • ember test
  • ember test --server


  • yarn lint:js
  • yarn lint:js --fix


  • ember build (development)
  • ember build --environment production (production)


Deployment to Heroku occurs automatically for the master branch.

Further Reading / Useful Links