* We're actively working on a Getting Started Guide with live examples that walks the user through building a new application from scratch.
* We're continuing to improve our guides to talk through areas that might be confusing for new developers, like the naming conventions we use in Ember
* Ember 1.0 will feature the return of the Starter Kit, which directly addresses the concerns by the OP. We removed it temporarily to bring it up to date with the most recent idioms, but it will be coming back very soon. This was a hard decision that sucked, but leaving around an out of date starter kit seemed worse than removing it.
I take this concern very seriously, and hope that people will continue to give us a look as we improve the experience for new users.
It's nice to be able to take a look at something that works and is simple enough to read through in one glance and go "Ah hah!"
Bootstrapping an editor session is as simple as POST'ing a simple form targeted at that url.
I would really love to see the Ember.js community get some use out of Plunker. (@filearts on twitter if you'd like to chat).
You can see a list of features on the development version of the site at: http://beta.plnkr.co/ These include:
* Real-time code collaboration
* Fully-featured, customizable syntax editor
* Live previewing of code changes
* As-you-type code linting
* Transparent translation of intermediate languages like Coffee-Script, Typescript, Sass, etc (with sourcemapping included where available). This means you create 'app.coffee' and ask for 'app.js' in your html and you are served the compiled version of 'app.coffee' as well as its sourcemap.
* Forking, commenting (not done yet) and sharing of Plunks
* Fully open-source on Github under the MIT license
Also, there is both a Google Group (http://plnkr.co/discuss) and github repo (https://github.com/filearts/plunker).
That being said, neither of these properly address your question. I will push out an about page as soon as I can.
I would build it myself, but I personally haven't been able to become proficient enough with Ember (in the admittedly limited amount of time I have tried mastering it) to do so.
Edit: Now that I think about it, aren't DHH's Rails screencasts considered one of the reasons why Rails got as popular as it did?
Unfortunately, both cost money at the moment but I've heard they're worth it.
Edit: Now that I'm rereading my post, it sounds really entitled and arrogant when it was not supposed to. It's more like "if I were on the Ember team, here's what I'd try to do".
Try talking like a human or at least a developer and not a marketroid.