Ember is a client-side MVC framework. It provides a model layer, routing, and templates to ease the task of creating a SPA, while using best practices.
- None.
By the end of this, developers should be able to:
- Explain the value of routes on for a client application.
- Diagram the parts of Ember and describe how they interact.
- Recall which parts of Ember are responsible for which tasks when building a feature.
- Fork and clone this repository.
- Change into the new directory.
- Create and checkout a new branch, named
response. - Follow the directions given in
study.md. - When finished, push to your fork and submit a pull request.
You may wish to refer to FAQs related to forking, cloning, and pull requests.
Source code distributed under the MIT license. Text and other assets copyright General Assembly, Inc., all rights reserved.