• Everyone is welcome in the Sass community, except those who are unwelcoming. Please read and follow our community guidelines.

    Still getting started? There are some great tutorials out there to get you on your feet. Want to learn more? There's some great Sass blogs (including a few particular articles we recommend reading), and even a few books about Sass to help you learn some new tips and tricks.

  • The Sass community is amazing. There are a number of frameworks that make using Sass simple. Want try Sass in Node, Python, or another framework? Check out the libSass resources.

    Thinking of contributing to Sass itself? We rely on everyone to keep Sass as stable as it is. Feel free to submit a patch via pull request to the Sass project.

    Want to create your own Sass implementation? Check out our implementation guidelines.

Sass Articles on the Web


Sass is an open source project and we encourage you to contribute. You can contribute with bug reports and feature requests or if you have code to contribute we will love you forever.

When adding bug reports, feature requests, or code there are a couple of primary branches we use.

The stable branch is where we do development on the released version. The majority of bug fixes should go here. If you're just reporting a bug add an issue and note the version of Sass where you experienced the issue in your comment. If you have some code to contribute, fork the stable branch and send us a pull request. We'll review your patch and either accept or decline with comments. All bug fixes must be thoroughly tested and the tests must pass the build on all supported versions of ruby.
The master branch is where we keep track of the next version of Sass. New feature requests should be made on the issue tracker and discussed with the core team before implementation begins to avoid wasted effort. Pull requests for new features should be made against the master branch. No change is allowed to break a stylesheet across sequential releases; every breaking change to the language must first be deprecated.

Pull Requests & Patches

Here are a few simple things you'll need to do when submitting a patch via pull request:

  • Write a commit message that is well-written, descriptive and contain proper grammar and punctuation.
  • Make sure the first line of your commit message is a short, full sentence.
  • Contain any appropriate unit tests in your commit
  • Add your changes to the changelog for the correct branch. The changelog is in doc-src/SASS_CHANGELOG.md
  • If your change is user-facing, update the appropriate section in reference documentation.
  • Don't combine several features or bug fixes into the same pull request.
  • All code is given a thorough review and will likely require several iterations before being accepted.
  • All code changes must be thoroughly tested and the tests must pass the build on all supported versions of ruby.


Sass Blogs

Sass Books

Projects & Frameworks

  • libSass — a CSS (and Sass!) authoring framework
  • Compass — a CSS (and Sass!) authoring framework
  • Susy — a responsive grid layout built for Compass
  • Bourbon — a lightweight mixin library
  • Neat — a mixin-based grid layout system
  • Sache — a place to find Sass and Compass extensions
  • SassMeister — a tool for trying Sass in the browser
  • Zurb Foundation — a responsive front-end framework
  • Rock Hammer — a starting framework with some basic styles for a project
  • Bootstrap — the ubiquitous framework… this time written in Sass!
  • Gravity — a framework for making HTML5 websites with Sass
  • Inuit.css — a powerful, scalable, Sass-based, BEM, OOCSS framework
  • Flexible Grid System — power of limitless
  • SassDoc — A documentation tool for Sass