Compass & Codekit – either or, or both?
# December 19, 2012 at 1:37 am
(I’m a total part-timer front end web dev that is trying to learn SASS for fun, literally). I am trying to wrap my head around SASS and was drawn to Codekit, but of course I’m reading a lot about Compass.
In a nutshell, how are they different? I’m not getting it.
Example, I’m working on a new portfolio site for myself using WP and Bones. Bones highly suggests Codekit for preprocessing, but I’m just curious where Compass comes into play, how it differs, etc?# December 19, 2012 at 2:59 am
Compass is a library for Sass. It has many useful mixins and functions. Codekit is an Mac OS X app that compiles Sass (and SCSS) files to pure CSS. You can use Compass with your Sass files in Codekit also.
1) Codekit = Compiler , app
2) Compass = Library, extension of Sass.# December 19, 2012 at 4:05 am
I’m not an expert but here is how I understand it so far:
SASS builds the base as the language extending CSS functionality. Files with .sass and .scss endings are both using SASS, but .scss looks a bit more like CSS syntax.
Compass then is an extension for SASS with useful stuff like CSS3 mixins which automatically deal with all the prefixes. You can use it if you want, but it’s not mendatory for working with SASS.
To compile SASS & Compass into CSS you need some sort of compiler. The best around I’d say is Codekit as it can also deal with many other preprocessed languages. There is also Compass.app which just deals with Compass & SASS. Hope that was useful ;)# December 19, 2012 at 11:35 am
Thank you both – I did a bunch of searches for “codekit vs compass” etc., but could not find a definitive comparison or definitions together.
This helps – I kinda feel like I need to merely learn SASS first, assess the use of it, then maybe move toward Compass.
(part of my confusion was, do I need to buy Codekit or just use Compass, etc – but I get it now).
You must be logged in to reply to this topic.