Are you getting started on your Ember.js adventure? Check out our official reading material:
Explore the available API of the various Ember ecosystem libraries. This is where you want to go to read in details about the various features, including example code.
Over the course of the years cruft inevitably sneaks into all software projects. In order to clean up outdated functionality and guide users, Ember has a deprecation process. You can read our deprecation guides for more information. You can find below more direct links to Ember and Ember Data versions.
One of the main strengths of Ember is how shared conventions enable developers to build on top of each other's work and improve the ecosystem for everyone. What follows are some of the projects more closely maintained by the several Ember teams.
Ember Inspector: A browser plugin/bookmarklet that helps you inspect and debug applications. Learn how best to use it in the Ember Inspector Guides.
Liquid Fire: A toolkit to add animations and transitions to your application. Check out their interactive documentation.
Ember Twiddle: Online code editor so you can share working snippets of code or reproductions of bugs. Try it out today!
In this section you will find applications that are maintained by the Ember.js teams with the help of contributors. While software is always a work in progress, the goal is to showcase patterns and solutions applied in real-world applications.
Whether you're simply interested in checking out how some feature is implemented, or you're looking to contribute, one of these projects might pique your interest!
If you've gone through our Tutorial you will already be familiar with this application! Super Rentals is a good starter project to get acclimated to the Ember.js way of doing things. In this repository you'll be able to see:
This is the application that the Ember.js team built to display our various release channels. It is slightly more complex than Super Rentals, and you'll be able to see:
Ember.js has a strong emphasis on Stability without Stagnation, which means that framework developers take great care when designing new functionality to make sure it fits with the existing functionalities, and provides a path forward for users to upgrade without being subjected to churn.
Ember.js also follow a community-driven process for its development that incorporates RFCs for features and deprecations and a six-week "train release schedule". Every six weeks, candidate features are reviewed and either deemed ready to be included in the stable release, or carry on in beta for another cycle until the next release happens.
In short, the best way to make sure you have a healthy application is to keep an eye on RFCs — remembering they document intent but not necessarily the final implementation, — keep your application clean of deprecations, and when possible test your application against beta and canary.
You can find more information at the Boston meetup Core Team panel