@xcambar wrote:
Exactly my situation.
I have found a decent, hard-won and mostly manual workflow for updating code and staying up to date myself, and it goes by:
- rejecting everything older than 3 months from search results (but as I know a bit of Ember's feature history, I can gut-feeling adjust the constraint)
- Read the blog posts: They are not optional. Most of the contents should end in the guides/API.
- Cherry-pick entries from the changelog: a more in-depth overview of the changes.
- reproduce with a JSBin or Twiddle: incredibly efficient because Ember is big and Ember apps are ambitious, therefore big(gish).
- read the RFCs. You can't possibly read every PR in ember.js and ember-cli repos, but RFCs are a great way to foresee deprecations and new features.
tl;dr; Spreading the docs between the blog, the changelog, the API, and the guides, plus the forever growing list of outdated resources is the source of all the documentation blur, I think.
my 2 cents. Feel free to reject Image may be NSFW.
Clik here to view.
