Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v1.11 doc is missing (updated) TodoMVC-style guide #10738

Closed
LionsPhil opened this issue Mar 27, 2015 · 4 comments
Closed

v1.11 doc is missing (updated) TodoMVC-style guide #10738

LionsPhil opened this issue Mar 27, 2015 · 4 comments

Comments

@LionsPhil
Copy link

v1.10 docs have a pretty good lead-in with a small sample application:
http://guides.emberjs.com/v1.10.0/getting-started/planning-the-application/
It covers good starting matter like:

  • Ember's opinion of what Model, View and Controller mean in a client-side world
  • Data-binding between the model and view in both directions (read and edit)
  • Binding of other actions ("delete completed")
  • Non-persistent state, and the concept that the controller is a proxy for the model which can manipulate and infer data for the view
  • Routing
  • Data persistence layers (fixtures for inital template work vs. moving to some real storage, although expanding it to continue on to a ReST endpoint would be even better)

In particular it's impressive that it starts with a spec and static mockup, because this fits the real world and keeps the whole thing in firm context of the end goal.

v1.11 docs don't seem to have these pages, but should have something covering the same ground, e.g. an updated version of the v1.10 app since for a simple example it can already cover a lot of angles.

(Raised as issue per locks' suggestion on IRC.)

@stefanpenner
Copy link
Member

i believe the appropriate repo for this issue is at: https://github.com/emberjs/guides

@LionsPhil
Copy link
Author

Ah bother, didn't realize that was split out. Want me to re-file over there? I'm not aware of any way to migrate issues in GitHub.

@stefanpenner
Copy link
Member

Ah bother, didn't realize that was split out. Want me to re-file over there? I'm not aware of any way to migrate issues in GitHub.

re-file is unfortunately the best option.

@LionsPhil
Copy link
Author

Done, closing as misfiled here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants