title: What is the best way to split up MVC controller functionality?
body: <p>When making Controllers, what are the best ways to split it up?</p>
  
  <p>If I have an admin section that has a bunch of .ascx web user controls underneath it and a few .aspx pages. Should I have one AdminController? Or should I have a Controller for each individual admin pages/web user controls?</p>
  
  <p>It seems as though being responsible for a single page's actions goes against one of the things MVC was trying to improve on from Web Forms. But at the same time, you don't want one Controller for your entire website...</p>
  
  <p>I understand what Controllers are supposed to do, but how much should one individual Controller be responsible for? What are the best methods for splitting up the responsibility of Controllers?</p>
  
  <p>Thanks,<br/>
  Matt</p>