– by Allison Wagner, from Cognition, September 2012
%li
= link_to "A Newb’s Guide to Syntactically Awesome Stylesheets (Sass) – part 1", 'http://unmatchedstyle.com/news/a-newbs-guide-to-syntactically-awesome-stylesheets-sass-part-1.php'
– by Dale Sande, from Unmatched Style, September 2012
%li
= link_to "Sass Sleuth: Debugging Sass in Webkit Browsers", 'http://www.mobify.com/dev/sass-sleuth-debugging-sass-in-webkit-browsers/'
– by Roman, from the Mobify blog, August 2012
%li
= link_to "Stop the Pain of Vanilla CSS and Get Relief by Adding Toppings with Sass", 'http://www.zurb.com/article/1031/stop-the-pain-of-vanilla-css-and-get-reli'
– by Chris, from the Zurb blog, July 2012
%li
= link_to "Building a Nested Responsive Grid with Sass & Compass", 'http://viget.com/inspire/building-a-nested-responsive-grid-with-sass-compass'
– by Trevor Davis, from Viget, May 2012
%li
= link_to "Nested Selectors: The Inception Rule", 'http://thesassway.com/beginner/the-inception-rule'
– by Mario "Kuroir" Ricalde, from The Sass Way, November 2011
%li
= link_to "Improve your Responsive Design Workflow with Sass", 'http://www.netmagazine.com/tutorials/improve-your-responsive-design-workflow-sass'
– by Ryan Taylor, from .net, October 2011
%li
= link_to "Getting Started with Sass and Compass", 'http://thesassway.com/beginner/getting-started-with-sass-and-compass'
– by Adam Stacoviak, from The Sass Way, June 2011
%li
= link_to "Getting Sassy with CSS", 'http://www.sencha.com/blog/getting-sassy-with-css/'
– by David Kaneda, from the Sencha blog, June 2010
%li
= link_to "Using Compass and Sass for your Next CSS Project", 'http://net.tutsplus.com/tutorials/html-css-techniques/using-compass-and-sass-for-css-in-your-next-project/'
– by Alex Coomans, from Net Tuts, August 2009
:markdown
Want to __learn more__? There's some great [Sass blogs](#Blogs")
(including [a few particular articles](#Articles) we recommend
reading), and even a few [books about Sass](#Books) to help you learn
some new tips and tricks. There are also a number of
[frameworks](#Frameworks) that make using Sass simple.
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](#Contribute) to the Sass project.
.content-primary
%h3#Articles Sass Articles on the Web
%ul.articles
- for article in data.community.articles
%li
%h3#Contribute Contribute
%p 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.
%h4= link_to article.url, article.name
%p= article.description
%p When adding bug reports, feature requests, or code there are a couple of primary branches we use.
%hr/
/ Will clean up these articles later. It'll be a curated list of
%dd 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 <a href="https://github.com/nex3/sass/issues"add an issue</a> and note the version of Sass where you experienced the issue in your comment. If you have a 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.
.features
%ul
%li
%ul
%li
= link_to "Sass vs. Less", 'http://css-tricks.com/sass-vs-less/'
– by Chris Coyier, from CSS Tricks, May 2012
%li
= link_to "Redesigning with Sass", "http://css-tricks.com/redesigning-with-sass/"
– by David Walsh, from CSS Tricks, October 2012
%li
= link_to "Using Bower with Sass & Compass", 'http://anthonyshort.me/2012/10/using-bower-with-sass-and-compass'
– by Allison Wagner, from Cognition, September 2012
%li
= link_to "A Newb’s Guide to Syntactically Awesome Stylesheets (Sass) – part 1", 'http://unmatchedstyle.com/news/a-newbs-guide-to-syntactically-awesome-stylesheets-sass-part-1.php'
– by Dale Sande, from Unmatched Style, September 2012
%li
= link_to "Sass Sleuth: Debugging Sass in Webkit Browsers", 'http://www.mobify.com/dev/sass-sleuth-debugging-sass-in-webkit-browsers/'
– by Roman, from the Mobify blog, August 2012
%li
= link_to "Stop the Pain of Vanilla CSS and Get Relief by Adding Toppings with Sass", 'http://www.zurb.com/article/1031/stop-the-pain-of-vanilla-css-and-get-reli'
– by Chris, from the Zurb blog, July 2012
%li
= link_to "Building a Nested Responsive Grid with Sass & Compass", 'http://viget.com/inspire/building-a-nested-responsive-grid-with-sass-compass'
– by Trevor Davis, from Viget, May 2012
%li
= link_to "Nested Selectors: The Inception Rule", 'http://thesassway.com/beginner/the-inception-rule'
– by Mario "Kuroir" Ricalde, from The Sass Way, November 2011
%li
= link_to "Improve your Responsive Design Workflow with Sass", 'http://www.netmagazine.com/tutorials/improve-your-responsive-design-workflow-sass'
– by Ryan Taylor, from .net, October 2011
%li
= link_to "Getting Started with Sass and Compass", 'http://thesassway.com/beginner/getting-started-with-sass-and-compass'
– by Adam Stacoviak, from The Sass Way, June 2011
%li
= link_to "Getting Sassy with CSS", 'http://www.sencha.com/blog/getting-sassy-with-css/'
– by David Kaneda, from the Sencha blog, June 2010
%li
= link_to "Using Compass and Sass for your Next CSS Project", 'http://net.tutsplus.com/tutorials/html-css-techniques/using-compass-and-sass-for-css-in-your-next-project/'
%dd The master branch is where we keep track of the next version of Sass. New feature requests should be made here. Similar to submitting patches, for the project and send us a pull request. We'll review your pull request and either accept or decline. If we decline we'll make a few comments in the pull request for changes or a reason the pull request was declined.
%p 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.
%p When adding bug reports, feature requests, or code there are a couple of primary branches we use.
%dd 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 <a href="https://github.com/nex3/sass/issues"add an issue</a> and note the version of Sass where you experienced the issue in your comment. If you have a 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.
%dd The master branch is where we keep track of the next version of Sass. New feature requests should be made here. Similar to submitting patches, for the project and send us a pull request. We'll review your pull request and either accept or decline. If we decline we'll make a few comments in the pull request for changes or a reason the pull request was declined.
%h3#PullRequests Pull Requests & Patches
%p Here are a few simple things you'll need to do when submitting a patch via pull request:
%ul
%li Write a commit message that is well-written, descriptive and contain proper grammar and punctuation.
%li Make sure the first line of your commit message is a short, full sentence.
%li Contain any appropriate unit tests in your commit
%li Add your changes to the changelog for the correct branch. The changelog is in <code>doc-src/SASS_CHANGELOG.md</code>
%li If your change is user-facing, update the appropriate section in reference documentation.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
₍˄ุ.͡˳̫.˄ุ₎