Routing Guide seems Backwards

[sgharms]

After some amount of pain involved in getting an Ember.Router working, I think the approach here is wrong. Starting at the templates and working backward to the router is, uh, backward.

A more natural point of introducing the concept is the Ember.Router or URL de-structuring. Based on @wycats' gists, it seems like the focus should be on serialization of state (i.e. the Router). The templates and references to {{outlet}} come too early.

If readers were to be made to what the route was, and that some assumptions were made in terms of naming and view, and that based on those assumptions a given template file was going to be used, then I think the message of this document would come across more clearly.

This may just be my particular learning style, but i found myself acking the source a bit too often for this guide to merit a "done" status. Any complaints with my taking a stab at it from another direction?

Steven

[wagenet]

Guides have been re-worked. Please file a new ticket if you still see problems.