How to compile scss files

[pattern-lab]

How to compile scss files

[robrecord]

Yes, mightily confused about why my sass/scss didn't get compiled. Using node it shouldn't be hard to add a gulp/grunt task for this by default.

[heroheman]

For anyone else wanting a small script file for (Vanilla) SASS Watching , ive "created" a small watch script and started it with the other scripts

#!/bin/sh 
DIR="$( cd "$( dirname "$0" )" && pwd )"
sass $DIR/../source/css/style.scss:$DIR/../public/css/style.css
sass --watch $DIR/../source/css/style.scss:$DIR/../source/css/style.css

Maybe useful for someone.

[bradfrost]

Hey @jamiebrightlemon!
The project's default CSS files can be found in source/css and that's where you should put your SCSS files. You'll see the default SCSS files in there, but please don't use them. Pattern Lab just gives you enough to get started with, but isn't a requirement.

Pattern Lab doesn't compile or watch for changes in SCSS. If you're looking to do that, I'd recommend checking out a tool like Codekit. That's what I use and it works wonderfully.

Moral of the story is that Sass is pretty cool and I enjoy using it, but it's not a requirement of Pattern Lab. Hope this clarifies things a bit.

[magique]

Hi @bradfrost
Thanks for your speedy response.

However I'm not looking to use Codekit use to compile the SCSS.

I usually use a config.rb file in the root of my project (and then use compass watch) - is this how you would recommend doing it also with this?

Also, why shouldn't we be using the default SCSS files?

Thanks
Jamie

[dmolsen]

@jamiebrightlemon -

from a technical standpoint compass should work just fine.

[magique]

Thanks @dmolsen
I've just used a standard config.rb file to achieve this.

I'm still not sure why @bradfrost mentioned about not using the default files?

This is a great starting point for creating a live style guide that also stands as a prototype! Many thanks for all your hard work on this.

Jamie

[dmolsen]

You're welcome :) We have some cool features in the pipeline so hopefully it only gets better.

[bradfrost]

I'm still not sure why @bradfrost mentioned about not using the default files?

The reason why I don't recommend not using the default styles is that they're just a starting point, they aren't cross-browser tested, and I believe CSS should be authored the way that makes the most sense to the author, not because I wrote things a certain way.

I'll try to articulate this a little better in the future, but in the meantime, you're obviously free to use the style structure I set up. But just don't feel you have to do things that way.

[dmolsen]

@heroheman -

thanks. we'll have to see if we can pull this into the docs so it gets more visibility.