How do you architect large websites with Ember?


#1

What’s the best approach when designing large Ember sites?

For example, if I were to build a social network with Ember, there could be a lot of different pages (templates), which wouldn’t be needed a lot of the time.

For example, if there was an FAQ section of the website for help/support which featured lots of interactivity, I wouldn’t want to send the templates to every visitor. How do I manage this? Do I use some kind of build tools to only send some main templates by default, then lazy load the uncommon ones, or let my backend load another page with a different Ember application or (and how would you manage routes between what Ember handles and the backend handles)…?