Modular Extensions - HMVC version 5.3

[eluser]Andy78[/eluser]
I'm working on a social networking/dating type of site that will have main page and side bar filled with widgets and so on. Similar in structure to this joomla site of mine but probably not as complicated at first.

So far im set-up and running with CI2, Modular Extensions - HMVC and ion-auth as a working module. I plan to design each widget as its own module and split the site up into an a user facing frontend and admin backend which I plan to develop overtime to have control over every aspect of the site.

My question is how to best separate the front end from the administration end Iv read this article and I think the third option is probably best for my site but when he says:

I have a single admin.php controller in the main controllers folder to act as the default admin page which will handle login, logout and the main dashboard.

I'm not sure how to implement this in Modular Extensions - HMVC. Obviously Id have a main admin controller to act as the main admin dashboard and also a main front end controller to act as the home page and load all the other modules in as widgets etc. But where should these main controllers go? each in there own modules or outside the actual module structure?