Closed raq929 closed 7 years ago
As a newcomer to this repo, I do agree that it seems counterproductive to introduce this new technology by first talking about how it no longer works. However, I also feel that the inclusion of Ember 1.0 will be informative for understanding why Ember 2.0 is the way it is. Especially considering that we expect more change to come soon.
In my opinion, the pedagogical purpose would be better served if the order was switched. The first thing developers should know if how is DOES work (i.e. use Components, Templates), and then explain that Ember is currently undergoing an evolution, and what it was formerly.
That's an interesting idea @neugierige. I'd have to see how it flowed, but I think you might be on to something. "Here's how it works with pods." THEN "Here's what you might see in documentation/stack overflow.
Can this be closed per https://github.com/ga-wdi-boston/ember/pull/27?
https://github.com/ga-wdi-boston/ember#layers-of-an-ember-application Some of it clearly needs to stay in so that when they make searches they know what is relevant to them or not. Some of the material can likely be removed? (Per conversation in planning for 015) @jrhorn424 @payne-chris-r @gaand