Add tutorial for building your first Ember app #445
Comments
|
Meanwhile is there an up to date tutorial somewhere on the net ? I have to create an internal app with EmberJS and most of the resources except the official docs seems outdated. |
|
I'm not sure, but I'd start with something like this search (the date is arbitrary). |
|
Thanks ! Yes it gives better answer :) |
|
@ygrenzinger check http://emberwatch.com/books.html for more suggestions, of the first four I'm not unfamiliar with Puri's but the others should be relatively up to date. |
|
Oops, didn't see this issue, #565 is a duplicate. Closing that and subscribing to this. Also willing to help out with writing a basic tutorial. |
|
Thanks for the offer @wldcordeiro! Let me get back to you within the next few days. |
|
@michaelrkn no problem. Here's an idea of a TOC for the tutorial, I'm not super familiar with Ember myself but I think that could be useful when writing beginner tutorials.
|
|
@wldcordeiro feels backwards to me to talk about models ahead of Routes, which is where everything falls from in Ember. I also don't like the idea of interacting with them in the console that much, what's your idea behind that? |
|
Agree with that. Routes are more fundamental to the overall architecture than models. |
|
I also agree that Routes should first be introduced since it is more fundamental to Ember. Models will come in later. I find a 'slice-of-things' approach effective where the new user is exposed to the fundamental Routes --> Template then revealing the Controller and then eventually the Model. Components needs to be established next since we are supposed to have transitioned to that and I think Services has to be introduced along clarifying how it will be used in the world of components going routable. Ensuring a clear understanding on the functional relationship between these sure does provide a sound foundation into digging deeper on some more specific mechanics provided by each. This could progress into further 'tweaking' each aspect to serve usual application requirement scenarios. Tests I think should not add to the initial burden of learning the fundamental concepts that's why I think it would be more beneficial and eventually satisfying for it to be introduced later. Satisfaction is a rather often disregarded aspect when providing support to the community of developers (especially new ones). There is a big possibility of developers disregarding these because of their natural technical bias of knowing things already clouding the stance to take on the perspective of new developers to Ember who have definitely have a different 'lens' coming into the Ember development community. Perhaps the use of pods could further be emphasized now that it's already 2.0. The concept and implementation of pods in relation to the components can be established furthermore. The different areas of the tutorial can be 'sprinkled' with references to the different guides and API docs on instances where a more in-depth explanation and examples are necessary. FAQs can be compiled and categorized in the site and in fact could be ID'd so they can be referenced in the Slack channel. I could see questions along similar veins that @tombot could eventually grab hold of to lessen the repetitive manual provision of answers. We should make use of this mechanism otherwise I feel it funny for masters of automation not to apply this to our own support to the community. References will provide some external links to further enrich their learning experience. The idea of a tutorial could provide a great medium to deliver a progressive story line. I would be glad to further look into the 'revival' of the tutorial by @michaelrkn & @poteto and hopefully be able to contribute to that effort. |
I like that idea, I think it'd be cool to show the new user first how to make an app the straight forward way and then how to port it to use pods? |
|
@wldcordeiro: I think your list is great and should be taken in the context of good intention. It's an important step towards coming up with something and you should be thanked for it 👍 |
|
@wldcordeiro: Exactly. I think the pods have is important in the implementation of Components and in architecting an ambitious Ember app. I hope we also get 'meta' as in we also do an ambitious guide/tutorial to creating ambitious Ember apps 😉 |
|
👍 |
|
There should also be somewhere in the tutorial where we're actively using Computed Properties, and Computed Property Macros, especially those like filter. Also, I'd love to be involved in this. |
|
@bravely Thanks for offering to help! There are already a couple people working on the tutorial, but we'd love to get your help with any issue labeled help wanted. |
|
"we'll hopefully have something to show before too long!". When, more or less, do you expect this to be? I would favour having bits which are ready released sooner rather than waiting for something perfect later. Perfect is the enemy of the good and all that. |
|
@githubshrek We all would. Please be patient - the people working on this are all volunteers, and it is a big project. Several people have volunteered to help out and then not been able to do so, but we have someone actively working on it right now and the first PRs should come in next week. |
|
@michaelrkn is there a branch they're working on or in a fork? |
|
A new tutorial is very much needed, and something that I really missed when trying to learn Ember recently. Will go through and read the other PRs and leave some comments 👍 |
|
+1 from an Ember newbie |
|
I understand that there are volunteers writing. But isn't it possible to do things in a wiki style, where every change gets put live straight away. It was 13 days ago that it was said above "the first PRs should come in next week.". I had a week to work on EmberJS and that has now gone and been lost because there was nothing to help me get started. It would be better at least if there was a 1-liner that said: if you're a newbie, use Ember 1.3 where there is a tutorial. |
|
@githubshrek is an open PR for this here: #801 |
|
Between this tutorial and the getting started guides, I was wondering if there's place to discuss concepts in greater detail -- the biggest issue I had when starting was that I didn't quite understand how everything worked together. It would be nice to have a one pager that has a (fairly detailed) lifecycle diagram (or explanation) from literally when you hit a url to what gets rendered on the page. Not sure if this makes sense in the guides or in a tutorial. |
|
@Joelkang a related pertinent question is who would write that ;) |
|
Gosh @michaelrkn, I was going to link to that image. Can't you give me three minutes headstart? ;-) |
|
@acorncom no way! ;) |
|
@michaelrkn yisss. Because I'm largely a visual learner these things help me so much -- more detailed lifecycle diagrams for routers (before/afterModel, redirecting, storing and replaying transitions) and components (didReceiveAttrs etc.) would all be super useful. And I'm more then willing to help add / edit / illustrate. |
|
Awesome! Feel free to open PRs. On Saturday, September 26, 2015, dudboi notifications@github.com wrote:
|
Once upon a time, the guides opened with a tutorial that showed brand new Ember developers how to build an app from start to finish. As that tutorial became increasingly out of date, it was removed from the guides with the intent of replacing it with an up-to-date tutorial. Much time has passed, but at long last @poteto has spearheaded the creation of this tutorial. I (@michaelrkn) am helping her out, and we'll hopefully have something to show before too long!
The text was updated successfully, but these errors were encountered: