So, funny @JulianLeviston ropes me into this, I actually solve this exact problem in my application. Visit EmberFlowsGenerator and then click the headers for each individual section. Ignoring the fact that I’ve not properly handled the CSS, you get all of the things you might imagine wanting.
This is implemented using a combination of:
https://github.com/nathanhammond/ember-flows-generator/blob/master/app/templates/index.hbs
https://github.com/nathanhammond/ember-flows-generator/blob/master/app/router.js
In short, make each section responsible for itself, and then create a separate “dashboard” route that coordinates their inclusion and manages their combined state. It’s like having iframes but way better.
Disclaimer: I’ve not yet started to try and pass models through to children with this solution, or handle child outlets without routing. The first shouldn’t be bad, you can pass {{render}} a model. The second layer will probably require a clever Ember plugin to change how outlets are populated. @machty knows where the bodies are buried in the router and I fully intend to try and snag some of his time to solve that problem at some point in the future.
To get rid of a typo I have to add something.