I've been following some tutorials to setup a custom section in the backoffice. I've managed to create a new section, add a tree controller and load a custom angular view.

This works fine for me if the view I'm using shows pretty basic content, but I question what the best practices are for handling more complex situations?

In my current scenario, I have an angular view that displays a list of members. But what if I want to have this listview click through to member details?

At the moment I handle all the functionality within a single controller, showing the list view when I want to list all members, then hiding it and displaying a single member's details on the page when I drill down, but I'm not sure if this is ideal.

Since angular apps pretty much work off a single html page, loading in the appropriate views, I wonder if this is the approach I should use for my custom sections? Should one of my custom section views be treated as a standalone angular app? ie. should I use angular's routing and state provider to handle all the different views I may use, or should it be divided out into separate views, using umbraco's routing to handle the different sections?