Good Morning All,

I'm relatively fresh when it comes to using SASS and Compass for building CSS, so I was curious why this is documented as a part of the theme. At least on my current local development set-up I write with SASS and Compass, compile the code and upload the output CSS to my site. Is the addition of SASS and Compass to this theme simply allowing for the compiling to happen through Drupal?

My apologies if this is a silly question, I'm just trying to understand more about how the pieces fit together.

Many thanks in advance!

Brian

CommentFileSizeAuthor
#2 sass.gif13.59 KBericxb

Comments

tregeagle’s picture

tregeagle commented
Component: Miscellaneous » Documentation

Hi Brian,
To help you fit the pieces together, my dev workflow goes something like this:

  1. I run an instance of the website I am building here on my workstation.
  2. I also set up a dev version on my server.
  3. I synchronise my local version with the dev site using git.
  4. I develop the CSS on my local machine using SASS.
  5. I preprocess the scss files using compass watch
  6. This way I can test on my own workstation as I am building
  7. When I sync with my server I usually exclude all the sass-cache stuff but I leave all the other sass stuff for future use

When more than one dev is working on a theme it can be good to preprocess the css on a dev server. I can think of no compelling reason to preprocess css on your average live server though.

I hope that helps.

ericxb’s picture

ericxb commented
StatusFileSize
new sass.gif13.59 KB

Using sass/compass is optional. You can just edit the css directly as you see fit; delete, the compass files and forget they were there. Drupal doesn't grok sass and only uses the compiled css files.

However, I think if you spend the time to learn sass/compass (it's pretty easy if you already know CSS), you'll glom onto it pretty fast. You do have to install sass and compass on your devel machine; but you end up with much more robust, more easily maintained css.

Their logo is really cool too sass logo

danlinn’s picture

danlinn commented
Status: Active » Closed (works as designed)

The reason I originally included it and continued to is because the SCSS in this theme allows for quick setting of some variables to get a layout going quickly, without having to do fancy margin math, etc.

We actually only commit the SCSS to github because you can get some crazy merge conflicts with the output CSS. We then build our SCSS as part of our Capistrano build steps. But that's another story.