Move Source Files (e.g. JavaScript and Sass) to separate directories

[salcode]

Currently, the Sass files are in css/sass/. The pain point here is I recently had a project where I was manually deploying the code by dragging-and-dropping folders and if I made a CSS change and dragged the css folder, I was re-uploading all the Sass each time, which was a lot of extra files.

If we move the Sass files to another directory (e.g. resources/sass/), we can still write the finalized CSS to css/ and css/ becomes nearly empty and much easier to update.

We could be able to do the same thing with JavaScript (i.e. move js/vendor/ and js/custom to resources/, only having the compiled files in js/).

Note: If the css/ and js/ directories become empty in the repository (i.e. only containing something when the grunt creates the files, we'll need to add something like .gitkeep to the directory). See http://stackoverflow.com/questions/7229885/what-are-the-differences-between-gitignore-and-gitkeep

[unwiredtech]

I used your framework last month and it is necessary to update?

Another question; Javascript Vendor folder is not compiling, I tried to add to folders of JS libaries but they are not being uglified or minified.

[salcode]

Hi @unwiredtech,

In order to keep the conversation on this issue focused on whether or not to move source files to separate directories, I've moved your questions to their own issues. See #147 and #148

Thanks.

[salcode]

I find I spend much more time with theme CSS than JavaScript.

For the CSS, I'm thinking about changing things so I have two root folders (sass and css), which is inspired by how _s has a root directory for their Sass files. Going this route, we'll need to add a file to the css directory (i.e. .gitkeep, .gitignore, or README.md which are all competing standards for including a empty directory in a Git repo).

I'm not sure how I want to handle the JavaScript folders.