Code Organization

edited October 2012 in General
I'm copying my SO question here to reach a wider audience of enyo devs:

I'm using Enyo to build a web application; a "normal" way of organizing the files might look like this:

CSS: webapp/css
JS: webapp/js
Other stuff: webapp/assets

One of my co-workers had a seemingly good idea to co-locate the Javascript and CSS, so that a Javascript file (e.g. webapp/js/MyView.js) would have its CSS analog located in the same folder with it (webapp/js/MyView.css). This seemed like a good idea, but since I've never seen this done before I wanted to get a second opinion from the internets.

So, internets, is this a good way to organize Javascript and CSS code? Why/why not?


Sign In or Register to comment.