Moocher File Structure

Most of the Moocher team is familiar with the Model View Controller framework from past work with Ruby on Rails. We have decided to modify this framework for Moocher. The main change we are making is the combination of the controller and the view. We will also have a model for each view/controller which will contain all functions needed to interact with our database or outside interfaces/API's. However, we will also have "models" for external interfaces, API's, or even large pieces of functionality such as mapping, pagination, emailing, etc. Apart from the Model View Controller framework we're also splitting up the CSS and Javascript per view/controller so that each page has a definite location for all of it's functions, styling, and scripts. We're hoping this move will minimize the amount of people editing a single file at a time. A visualization of the Moocher file structure can be seen below: