# Opinions please

**URL:** <https://discourse.cakephp.org/t/opinions-please/4438>\
**Category:** Performance\
**Created:** [June 21, 2018, 11:24am UTC](https://discourse.cakephp.org/t/opinions-please/4438 "2018-06-21T11:24:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![j-bone](https://avatars.discourse-cdn.com/v4/letter/j/cc9497/32.png) [@j-bone](https://discourse.cakephp.org/u/j-bone)\
**Post date:** [June 21, 2018, 11:24am UTC](https://discourse.cakephp.org/t/opinions-please/4438/1 "2018-06-21T11:24:49Z")

</div>

What is your opinion on having a separate dashboard controller vs. a dashboard action in any given controller?

---

<div class="post-metadata">

**Author:** ![FinlayDaG33k](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.cakephp.org/finlaydag33k/32/1049_2.png) [@FinlayDaG33k](https://discourse.cakephp.org/u/FinlayDaG33k)\
**Post date:** [June 21, 2018, 12:32pm UTC](https://discourse.cakephp.org/t/opinions-please/4438/2 "2018-06-21T12:32:10Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![j-bone](https://avatars.discourse-cdn.com/v4/letter/j/cc9497/32.png) [@j-bone](https://discourse.cakephp.org/u/j-bone)\
**Post date:** [June 21, 2018, 1:31pm UTC](https://discourse.cakephp.org/t/opinions-please/4438/3 "2018-06-21T13:31:14Z")

</div>

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.