-
API docs
-
How to bootstrap a project
-
Application structure (M/V/C layers and what they're for)
-
Getting started with Ember and Rails
-
Built-in controls
-
How events are handled and bubbled
-
Ember.ArrayController
-
Array observers, propagation and ArrayProxy
-
How the view layer works - 30,000 foot view
-
How to use state managers
-
Bindings and run loop overview
- Run once
-
Building Ember.js applications (conceptually, what needs to happen?)
-
Debugging
- Ember.Application and toString
- {{debugger}}
- {{log}}
-
Handlebars composition
-
Handlebars helpers
- paths
- binding aware
-
View layer lifecycle hooks
-
Others
- Routing
- Persistence
- jQuery.ajax
- Equivalent of Backbone sync
- ember-data
- ember-debug
Created
February 18, 2012 01:54
-
-
Save tomdale/1856842 to your computer and use it in GitHub Desktop.
Ember documentation TODO
When dealing with state managers and/or Rails, it would be helpful if best practices for authenticating a user against the back end server were explained. Perhaps an example where unauthenticated users are presented with only a login form and once authenticated, the rest of the interface appears with their name in the corner and the option to log out.
Hi there, what I would find really useful is a list of available plugins.
For instance, I have recently discovered this: http://ghempton.github.com/ember-layout-example/ which I think is really interesting.
@johngouf there are some useful links in the Ember.js wiki
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi guys! Yesterday, i wrote a post about how to contribute to Ember docs :)