What is your opinion on having a separate dashboard controller vs. a dashboard action in any given controller?
Depends on what you’re trying.
I currently am working on a dashboard myself, but I keep stuff to their respective controller.
So the main dashboard stuff (like checking whether the user has access to the dashboard itself) is in the dashboard controller, while the stuff to add, edit or remove a blog article is being done in the blog controller.
Letting the OO principle of loose coupling and tight cohesion guide my overall design decisions. I now feel compelled to break the design down into areas of responsibility, and create MVC objects to handle those responsibilities.
Thanks for your input! Much appreciated.