What you see in site is something like this:
Each of those module directories contains a manifest which tells MvcEx where to get the controller actions from for those views.
Effectively this means that in order to add a module to the application you have to add a views folder for it under the /site/ structure, and a binary containing the actions.
While it would be more separated to have the binaries provide the views in a neat little package, it doesn't provide a good development experience, and because our multi-tenant software is entirely internally developed it doesn't matter what the main application
always has all of the modules nested inside of it, as what really matters is whether they're turned on or not in a configuration.
I hope that makes sense?