Even this is use a EmberCLI and Broccoli instead of Grunt (or similar), I found very interesting for us in order to understand how organise our Ember/Rails project
I like a lot their clear division in two subfolder:
WebCalendar
| Rails
| Ember
After a meeting we decided to work with separate BE and FE, in different repos. And unify them via RestApi, just at the end.
Rails will take care of providing data in json file which Ember will use later on.
Good resource tutorial: http://reefpoints.dockyard.com/2014/05/07/building-an-ember-app-with-rails-part-1.html http://reefpoints.dockyard.com/2014/05/08/building-an-ember-app-with-rails-part-2.html http://reefpoints.dockyard.com/2014/05/09/building-an-ember-app-with-rails-part-3.html http://reefpoints.dockyard.com/2014/05/31/building-an-ember-app-with-rails-part-4.html
Even this is use a EmberCLI and Broccoli instead of Grunt (or similar), I found very interesting for us in order to understand how organise our Ember/Rails project
I like a lot their clear division in two subfolder: WebCalendar | Rails | Ember
https://github.com/bostonember/website
For what I got the division is more or less like:
Ember: Js test templates (with Handelbars) stylesheets define models (which kind of data they are) routers bower.json grunt.json
Rails: model data routes controller BE tests