Love the product, but wondering if you can modify the MVC convention so that it could behave in the following way? If I add a folder called Customer, that folder should encapsulate all the files and asset resources it needs for the Customer MVC page. The Controllers, Model, Views, Javascript, images. Hard disk space is cheap, but file management is expensive. This makes it much easier to deploy a new feature or roll it back. And you can have side by side old and new feature versioning by simply adding a number to the folder or renaming the folder. This also reduces the need to naming files awkwardly so that all the ducks line up. Yes, I think naming conventions are very important, but I'd also like to have everything that belongs together, to be together. Some JavaScript and/or images files that support the view should be with the view. Not in a global folder that is shared with everything. My 2 cents.