Using Pods in Ember

CurrentSetup.md

adapters/
  foo.js
  
models/
  foo.js
  
serializers/
  foo.js

utils/
  string/
    bar.js
    spam.js
  blah.js

services/
  queues/
    ham.js
  tasks/
    eggs.js
    fish.js
  gumbo.js

styles/
  app.css

helpers/
  foo.js

initializers/
  foo.js

instance-initializers/
  foo.js

transitions/
  foo.js

routes/
  components/
  application/
  index/
    /components
          /foo-component
    /all-authenticated-pods
  login/

IdealSetup.md

data/
  foo/
    model.js
    adapter.js
    serializer.js
    normalizer.js

utils/
  string/
    bar.js
    spam.js
  blah.js

services/
  queues/
    ham.js
  tasks/
    eggs.js
    fish.js
  gumbo.js

helpers/
  foo.js

initializers/
  foo.js

instance-initializers/
  foo.js

transitions/
  foo.js

components/
    foo/
      component.js
      template.hbs
      style.css

routes/
  application/
  index/
    /components
          /foo-component
    /all-authenticated-pods
  login/

why do you like data/foo/model.js over components/food/model.js?

i feel (personally) data should still be separate from routes or components, even if they are one-to-one used together?

+1 for the idea of having all the ember-data related stuff in a data pod