Q:

Controllers that have no model, Laravel MVC pattern

When designing laravel applications within the MVC pattern is it ok to have controllers that are not related to a model?
For example: My app has "Event", "User" and "Activity" models and related controllers. However, the application dashboard will be displaying a news feed of events, users and other items. Should I create a DashboardController class? Even if this does not directly relate to a model class?
Or is there a better way of doing this?

A:

Sure you can just make calls to the various models you need from the dashboard controller. I'm doing something similar myself at the moment and I have a dashboard controller in the works.
MVC doesn't mean that every C has to have an M or even a V. ;) Think of it as an overall pattern/structure and not that each has to be linked to the next level.

