Okay, I know nothing of how the Cloud runs this, but I can share how I use Scss. I am guessing it should be similar.
assets/
--components/
----mytheme/
------config.rb
------sass/
--------_base.scss
--------_desktop.scss
--------_mobile.scss
--------styles.scss
------stylesheets/
--------styles.css
------images/
------js/
Files with underscore do not get to be outputted to a css file with corresponding filename.
_base.scss will not be processed to become
base.css, which file will be useless to you anyway, and do clutter your folder if outputted.
These files are good for @media and what not.
Sass can "include" them to make up your final useful css file, in this case
styles.css
Each time you edit an underscored (or any) file that is used in your main scss file, this main scss file gets reprocessed, and your styles.css gets regenerated consequently.
Scss files go into a
sass folder, same level as the stylesheets, js and images folders.
The name of the folders and location can be set by you if you are using compass to watch and compile.
If for some reason this structure fails and compass is screaming green murder, just recreate the structure with compass on command line and copy back your files to their respective folders.
If using compass, you will need a
config.rb file to tell compass where your source files are and where to output them.
This
rb file is to be placed in the root of your template folder (mytheme).
A sample components/mytheme/config.rb for compass
http_path = "/" //tells compass that this is the beginning of your theme, and to find your folders within
sass_dir = "sass"
css_dir = "stylesheets"
images_dir = "images"
javascripts_dir = "js"
sourcemap = "true"
output_style = :expanded
# output_style = :compressed
I hope this isn't what you weren't looking for.