Hello, and welcome to the Ember Atlas, your one stop shop for navigating the world of Ember.js! This book is a community driven project dedicated to documenting all things Ember and providing a place share knowledge. It is meant to work like a curated wiki, gathering as much information as possible, while simultaneously ensuring that information is easy to browse and has an overall consistent flow.

We don't have much content yet, but in time we hope to make the Atlas one of the first places Ember users look whenever they have a question about Ember. If you'd like to contribute, check out the contribution guide or ping us on Discord! We always welcome new guides and ideas πŸ˜„

Why a Wiki?

You may be wondering why we need a community wiki. After all, Ember.js is a framework that is about conventions and zero-configuration, and the Ember guides are meant to be the canonical source-of-truth for those conventions. Doesn't having a community wiki run counter to that goal? Will it lead to more fragmentation in the ecosystem, and more confusion instead of less? We don't believe it will, and here's why:

The Atlas and the official Ember Guides are meant to serve different purposes. The guides must:

  1. Document the recommended, conventional, and beginner-friendly "happy path" for any given feature of Ember.
  2. Maintain documentation for all previous versions of Ember.
  3. Only document features that are part of the Ember framework itself, leaving out popular community addons and JavaScript libraries.
  4. Ship documentation that is thoroughly reviewed, triple checked, high quality, and battle-tested.

This sets a very high bar for the content that becomes part of the guides, and can be a daunting task to new contributors. It also prevents us from documenting many different intermediate and advanced user stories, which often involve various community addons or techniques.

β€ŒWe won't be able to cover every topic under the sun, but we can try to capture and organize as much community knowledge as possible, especially around common use cases and combinations. We can take the output of the many Discord conversations, Discourse posts, and Stack Overflow answers and put them in one place. We can help pick up the burden that popular addons have, making their tools easy to learn and approach and use with

β€ŒTo that end, the Atlas has some explicit goals and non-goals.β€Œ