Couldn't figure this from the docs:

My use case: A big SPA, with multiple "widgets" or "apps" on a page - Each with a controller, data and template. preferably each of those should be a view. Currently each template is loaded with `ng-include` which is both annoying, not seperating interests and not working very well, since the view controller might be initialized before the main ctrl is resolved - which is the reason we switched to UI router.most of the time the url aren't nested - for example a `/page` url can contain a Listview, a userview etc.

I want to move this to UI router (after I already moved the existing routing to UI router and checked everything is working correctly) and I'm not sure what is the right way to *compose* the widgets/views together. Should I use an abstract view that would hold `/page` template (and containing the routes) and set each widgets as a view inside this abstract? or would it work without the abstract. should I use named or nested (saw somewhere that named views are regarded a code smell, not sure why). what are the guidlines to choosing between the options and what are the best practices to set this up? I'll be happy for any advice about this.

Thanks!