Sass makes CSS fun again. Sass is an extension of CSS, adding nested rules, variables, mixins, selector inheritance, and more. It’s translated to well-formatted, standard CSS using the command line tool or a web-framework plugin.
Sass has two syntaxes. The new main syntax (as of Sass 3) is known as “SCSS” (for “Sassy CSS”), and is a superset of CSS’s syntax. This means that every valid CSS stylesheet is valid SCSS as well. SCSS files use the extension .scss.
The second, older syntax is known as the indented syntax (or just “Sass”). Inspired by Haml’s terseness, it’s intended for people who prefer conciseness over similarity to CSS. Instead of brackets and semicolons, it uses the indentation of lines to specify blocks. Although no longer the primary syntax, the indented syntax will continue to be supported. Files in the indented syntax use the extension .sass.
Sass can be used from the command line or as part of a web framework. The first step is to install the gem:
gem install sassAfter you convert some CSS to Sass, you can run
sass style.scssto compile it back to CSS. For more information on these commands, check out
sass --helpTo install Sass in Rails 2, just add config.gem "sass" to config/environment.rb. In Rails 3, add gem "sass" to your Gemfile instead. .sass or .scss files should be placed in public/stylesheets/sass, where they’ll be automatically compiled to corresponding CSS files in public/stylesheets when needed (the Sass template directory is customizable… see the Sass reference for details).
Sass can also be used with any Rack-enabled web framework. To do so, just add
“by require ‘sass/plugin/rack’ use Sass::Plugin::Rack
“
to config.ru. Then any Sass files in public/stylesheets/sass will be compiled into CSS files in public/stylesheets on every request.
To use Sass programmatically, check out the YARD documentation.
Sass is an extension of CSS that adds power and elegance to the basic language. It allows you to use variables, nested rules, mixins, inline imports, and more, all with a fully CSS-compatible syntax. Sass helps keep large stylesheets well-organized, and get small stylesheets up and running quickly, particularly with the help of the Compass style library.
Sass has two syntaxes. The one presented here, known as “SCSS” (for “Sassy CSS”), is fully CSS-compatible. The other (older) syntax, known as the indented syntax or just “Sass”, is whitespace-sensitive and indentation-based. For more information, see the reference documentation.
To run the following examples and see the CSS they produce, put them in a file called test.scss and run sass test.scss.
Sass avoids repetition by nesting selectors within one another. The same thing works for properties.
“ss table.hl { margin: 2em 0; td.ln { text-align: right; } }
li { font: { family: serif; weight: bold; size: 1.2em; } }
“
Use the same color all over the place? Need to do some math with height and width and text size? Sass supports variables, math operations, and many useful functions.
“ss $blue: #3bbfce; $margin: 16px;
.content_navigation { border-color: $blue; color: darken($blue, 10%); }
.border { padding: $margin / 2; margin: $margin / 2; border-color: $blue; }
“
Even more powerful than variables, mixins allow you to re-use whole chunks of CSS, properties or selectors. You can even give them arguments.
“ss @mixin table-scaffolding { th { text-align: center; font-weight: bold; } td, th { padding: 2px; } }
@mixin left($dist) { float: left; margin-left: $dist; }
@include left(10px); @include table-scaffolding; }
“
A comprehensive list of features is available in the Sass reference.
The Sass gem includes several executables that are useful for dealing with Sass from the command line.
The sass executable transforms a source Sass file into CSS. See sass --help for further information and options.
The sass-convert executable converts between CSS, Sass, and SCSS. When converting from CSS to Sass or SCSS, nesting is applied where appropriate. See sass-convert --help for further information and options.
To run the Sass executables from a source checkout instead of from rubygems:
“ cd
Maruku could not parse this XML/HTML: <SASS_CHECKOUT_DIRECTORY> $ bundle $ bundle exec sass ... $ bundle exec scss ... $ bundle exec sass-convert ...
“
Sass was envisioned by Hampton Catlin (@hcatlin). However, Hampton doesn’t even know his way around the code anymore and now occasionally consults on the language issues. Hampton lives in San Francisco, California and works as VP of Technology at Moovweb.
Natalie Weizenbaum is the primary developer and architect of Sass. Her hard work has kept the project alive by endlessly answering forum posts, fixing bugs, refactoring, finding speed improvements, writing documentation, implementing new features, and getting Hampton coffee (a fitting task for a girl genius). Natalie lives in Seattle, Washington and works on Dart application libraries at Google.
Chris Eppstein is a core contributor to Sass and the creator of Compass, the first Sass-based framework, and Eyeglass, a node-sass plugin ecosystem for NPM. Chris focuses on making Sass more powerful, easy to use, and on ways to speed its adoption through the web development community. Chris lives in San Jose, California with his wife and two children. He is an Engineer for LinkedIn.com, where his primary responsibility is to maintain Sass and many other Sass-related open source projects.
If you use this software, we’d be truly honored if you’d make a tax-deductible donation to a non-profit organization and then let us know on twitter, so that we can thank you. Here’s a few that we endorse:
Sass is licensed under the MIT License.