<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (Aetles)</title>
    <link>https://pinboard.in/u:Aetles/public/</link>
    <description>recent bookmarks from Aetles</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://dev.to/michaeldscherr/switching-from-sass-to-postcss-4p0c"/>
	<rdf:li rdf:resource="http://www.smashingmagazine.com/2015/06/17/responsive-typography-with-sass-maps/"/>
	<rdf:li rdf:resource="http://thesassway.com/intermediate/referencing-parent-selectors-using-ampersand"/>
	<rdf:li rdf:resource="http://thesassway.com/intermediate/using-source-maps-with-sass"/>
	<rdf:li rdf:resource="http://codepen.io/chriscoyier/blog/codepens-css"/>
	<rdf:li rdf:resource="http://css-tricks.com/sass-style-guide/"/>
	<rdf:li rdf:resource="http://zurb.com/university/library/42"/>
	<rdf:li rdf:resource="http://blog.teamtreehouse.com/sass-tip-double-ampersand-selector"/>
	<rdf:li rdf:resource="http://web-design-weekly.com/2013/05/12/handy-sass-mixins/"/>
	<rdf:li rdf:resource="http://breakpoint-sass.com/"/>
	<rdf:li rdf:resource="http://zmoazeni.github.io/csscss/"/>
	<rdf:li rdf:resource="http://blog.hull.io/post/46243434040/introducing-sass-getunicode"/>
	<rdf:li rdf:resource="http://typeplate.com/"/>
	<rdf:li rdf:resource="http://sassmeister.com/"/>
	<rdf:li rdf:resource="http://previousnext.com.au/blog/up-and-running-with-sass-in-drupal-7"/>
	<rdf:li rdf:resource="http://susy.oddbird.net/"/>
	<rdf:li rdf:resource="http://atomeye.com/accolades/sass/"/>
	<rdf:li rdf:resource="http://incident57.com/codekit/"/>
	<rdf:li rdf:resource="http://speakerdeck.com/u/imathis/p/sass-compass-the-future-of-stylesheets-now"/>
	<rdf:li rdf:resource="http://sonspring.com/journal/sass-for-designers"/>
	<rdf:li rdf:resource="http://sass-lang.com/"/>
	<rdf:li rdf:resource="http://www.zivtech.com/blog/css-suckers-introduction-sass-compass"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://dev.to/michaeldscherr/switching-from-sass-to-postcss-4p0c">
    <title>Switching from SASS to PostCSS - DEV Community 👩‍💻👨‍💻</title>
    <dc:date>2019-04-02T21:40:32+00:00</dc:date>
    <link>https://dev.to/michaeldscherr/switching-from-sass-to-postcss-4p0c</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Ever since PostCSS came out, I've exclusively used it for Autoprefixer. I didn't really dig into the power of PostCSS and how it could actually be a comparable solution to SASS.

This article will go into depth about my skepticisms, and how I was able to find solutions using PostCSS.

The Push
What originally considered me to switch was my interest in Tailwind CSS. I love the ideas of utility libraries, but found it difficult to sell to other developers. However, we've been looking for ways to optimize development time, so Tailwind felt like a good choice. It's built with PostCSS in mind, so I at least wanted to give it a try.]]></description>
<dc:subject>sass css tailwind postcss webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:dc91b9c338b5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:tailwind"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:postcss"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.smashingmagazine.com/2015/06/17/responsive-typography-with-sass-maps/">
    <title>Responsive Typography with Sass Maps</title>
    <dc:date>2015-06-25T20:11:06+00:00</dc:date>
    <link>http://www.smashingmagazine.com/2015/06/17/responsive-typography-with-sass-maps/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Managing consistent, typographic rhythm isn’t easy, but when the type is responsive, things get even more difficult. Fortunately, Sass maps make responsive typography much more manageable.
Writing the code is one thing, but keeping track of font-size values for each breakpoint is another — and the above is for paragraphs alone. Throw in h1 to h6s, each with variable font sizes for each breakpoint, and it gets cumbersome, especially when the type doesn’t scale linearly.]]></description>
<dc:subject>css design typography sass webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:e8176ed91261/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:typography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://thesassway.com/intermediate/referencing-parent-selectors-using-ampersand">
    <title>Referencing parent selectors using the ampersand character</title>
    <dc:date>2014-11-26T15:32:24+00:00</dc:date>
    <link>http://thesassway.com/intermediate/referencing-parent-selectors-using-ampersand</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Referencing parent selectors by using the ampersand (&) can be a powerful tool, if used right. There are simple uses of this feature as well as some very complex uses of this feature. In this post we will cover the basic uses of the ampersand (&) as well as link you to a post by Joel Oliveira that goes much deeper on the subject.]]></description>
<dc:subject>css sass scss webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:4e171a084d59/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:scss"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://thesassway.com/intermediate/using-source-maps-with-sass">
    <title>Using source maps with Sass 3.3</title>
    <dc:date>2014-10-07T14:48:47+00:00</dc:date>
    <link>http://thesassway.com/intermediate/using-source-maps-with-sass</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[One of the exciting new features in Sass 3.3 that every developer should take advantage of is source maps.

As CSS pre-processors, minifiers, and JavaScript transpilers have become mainstream it is increasingly difficult to debug the code running in the browser because of differences with the original source code.]]></description>
<dc:subject>css sass webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:335c07d929dd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://codepen.io/chriscoyier/blog/codepens-css">
    <title>CodePen's CSS by Chris Coyier on CodePen</title>
    <dc:date>2014-08-14T09:35:01+00:00</dc:date>
    <link>http://codepen.io/chriscoyier/blog/codepens-css</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Inspired by Mark Otto's tour of GitHub's CSS and Ian Feather's tour of Lonely Planet's CSS, I thought I would join the party and talk about how we do CSS at CodePen.]]></description>
<dc:subject>css sass webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:b28276fe27cc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://css-tricks.com/sass-style-guide/">
    <title>Sass Style Guide | CSS-Tricks</title>
    <dc:date>2014-06-28T22:04:50+00:00</dc:date>
    <link>http://css-tricks.com/sass-style-guide/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[With more people than ever writing in Sass, it bears some consideration how we format it. CSS style guides are common, so perhaps we can extend those to cover choices unique to Sass.

Here are some ideas that I've been gravitating toward. Perhaps they are useful to you or help you formulate ideas of your own.]]></description>
<dc:subject>css sass webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:598c47407b47/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://zurb.com/university/library/42">
    <title>ZURB University | 3 Minute Lessons</title>
    <dc:date>2014-06-03T22:24:43+00:00</dc:date>
    <link>http://zurb.com/university/library/42</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Semantic code makes your HTML leaner and more meaningful. Sass is a great tool to make that happen, and Foundation's Sass mixins help you integrate a grid with minimal fuss. The result is code that's easier to read and debug, which more accurately describes what you're trying to communicate.]]></description>
<dc:subject>sass css foundation webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:2c6da7c7b2ae/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:foundation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.teamtreehouse.com/sass-tip-double-ampersand-selector">
    <title>Sass Tip: The Double Ampersand Selector - Treehouse Blog</title>
    <dc:date>2013-12-29T00:26:50+00:00</dc:date>
    <link>http://blog.teamtreehouse.com/sass-tip-double-ampersand-selector</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[In Sass, the ampersand (&) symbol is used to reference the parent selector in a nested rule. For example, the following targets .btn on :hover:]]></description>
<dc:subject>sass css</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:0674874893cc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://web-design-weekly.com/2013/05/12/handy-sass-mixins/">
    <title>Handy Sass Mixins - Web Design Weekly</title>
    <dc:date>2013-05-15T13:25:17+00:00</dc:date>
    <link>http://web-design-weekly.com/2013/05/12/handy-sass-mixins/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Mixins are one of the most powerful features of Sass. Mixins allow for efficient and clean code repetitions as well as an easy way to adjust your code with ease. If you are using Sass in your development workflow, no doubt you are using some of the mixins that I have covered below but some might also be new and helpful.

]]></description>
<dc:subject>css webdesign sass webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:cb738513766c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://breakpoint-sass.com/">
    <title>Breakpoint</title>
    <dc:date>2013-04-29T14:54:23+00:00</dc:date>
    <link>http://breakpoint-sass.com/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Really Simple, Organized, Media Queries with Sass

Breakpoint makes writing media queries in Sass super simple. 

That just did two things that are really helpful. First, we reduced the media query down to the one value that really matters here, the min-width value. (You can also build complex queries and override the defaults. We’ll get to those.) And second, we gave that media query a meaningful name. And once we start calling media queries by name we can start managing them systematically.]]></description>
<dc:subject>css sass compass rwd</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:f7bbbf724942/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:compass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:rwd"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://zmoazeni.github.io/csscss/">
    <title>csscss by zmoazeni</title>
    <dc:date>2013-04-15T09:44:58+00:00</dc:date>
    <link>http://zmoazeni.github.io/csscss/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[csscss will parse any CSS files you give it and let you know which rulesets have duplicated declarations.]]></description>
<dc:subject>css css3 sass tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:3c17ada3e18a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.hull.io/post/46243434040/introducing-sass-getunicode">
    <title>hull, Introducing sass-getunicode</title>
    <dc:date>2013-03-27T08:25:13+00:00</dc:date>
    <link>http://blog.hull.io/post/46243434040/introducing-sass-getunicode</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[In case of you don’t know what it is, a pseudo-element creates an element and inserts it before or after the content of the element that you’ve targeted. Pseudo element content can be quite useful especially to insert glyphs and special characters in your page. But the weird thing is that the value of the content property must be an escaped reference to the hexadecimal unicode character value.
I thought it would be faster to skip this step and do it directly in my stylesheet with the help of my best friend, Sass. That’s why I wrote this small Sass plugin which allows you to do it.]]></description>
<dc:subject>css design sass unicode</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:cec0e3e51cf8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:unicode"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://typeplate.com/">
    <title>Typeplate » A typographic starter kit encouraging great type on the Web</title>
    <dc:date>2013-03-05T10:14:05+00:00</dc:date>
    <link>http://typeplate.com/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Frameworks make decisions for you about how to organize, structure and design a site. Pattern libraries don’t separate styling and markup, making them tough to use in a truly modular fashion. We weren’t satisfied, so we made a thing that doesn’t do that.

Typeplate is a “typographic starter kit”. We don’t make aesthetic design choices, but define proper markup with extensible styling for common typographic patterns. A stripped-down Sass library concerned with the appropriate technical implementation of design patterns—not how they look.]]></description>
<dc:subject>css design fonts typography sass</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:d88672a838f8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:fonts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:typography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sassmeister.com/">
    <title>SassMeister | The Sass Playground!</title>
    <dc:date>2013-01-30T09:42:26+00:00</dc:date>
    <link>http://sassmeister.com/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[SassMeister is a playground for Sass. Add some Sass and SassMeister will show you the rendered CSS. SassMeister supports both Sass and SCSS syntaxes, all output styles, and a growing number of Compass extensions and Sass libraries. ]]></description>
<dc:subject>css sass scss compass webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:ebc6bf08cd92/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:scss"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:compass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://previousnext.com.au/blog/up-and-running-with-sass-in-drupal-7">
    <title>Up and running with Sass in Drupal 7 | PreviousNext</title>
    <dc:date>2013-01-08T09:03:56+00:00</dc:date>
    <link>http://previousnext.com.au/blog/up-and-running-with-sass-in-drupal-7</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[SASS is Syntactically Awesome Stylesheets, and a powerful way to streamline your Drupal theme's CSS. Based on CSS, the learning curve is not too steep for a seasoned front-end developer. In this post, get an introduction to the basics of SASS and how to get your development environment up and running.

]]></description>
<dc:subject>drupal css sass webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:ddd20dab9a1e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:drupal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://susy.oddbird.net/">
    <title>Susy: Responsive grids for Compass</title>
    <dc:date>2012-05-30T06:39:32+00:00</dc:date>
    <link>http://susy.oddbird.net/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[The web is a responsive place, from your lithe & lively development process to your end-user's super-tablet-multi-magic-lap-phone. You need grids that are powerful yet custom, reliable yet responsive.

Susy grids are fluid on the inside, ready to respond at any moment, but contained in the candy shell of your choice, so they respond how and when and where you want them to.

We don't design your site or dictate your markup, we just do the math and get out of your way.]]></description>
<dc:subject>compass css framework grid sass</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:955b89bb7ded/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:compass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:framework"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:grid"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://atomeye.com/accolades/sass/">
    <title>Sass &amp; Compass: Why You Hatin’? : Atomeye</title>
    <dc:date>2012-02-01T16:13:00+00:00</dc:date>
    <link>http://atomeye.com/accolades/sass/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Similar to the way developers use programming languages to generate valid HTML, Sass and its first cousin, Compass, combine to provide a powerful toolbox for generating valid CSS. It’s a win-win: developers can now use features like variables to write faster and more easily maintained code and the resulting CSS will work in browsers exactly as before. What’s not to love?

Well, this is the Internet and some people don’t love it. Rather than write another overview of the most advertised features of Sass, I thought I’d address a few of its critics and provide some tips for those still unsure about using it.]]></description>
<dc:subject>sass css compass</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:f6320cbcec4e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:compass"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://incident57.com/codekit/">
    <title>CodeKit — THE Mac App For Web Developers</title>
    <dc:date>2012-01-23T13:23:35+00:00</dc:date>
    <link>http://incident57.com/codekit/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[CodeKit automatically compiles Less, Sass, Stylus, CoffeeScript & Haml files. It effortlessly combines, minifies and error-checks Javascript. It supports Compass. It even optimizes jpeg & png images, auto-reloads your browser and lets you use the same files across many projects. And that's just the first paragraph.]]></description>
<dc:subject>css javascript less sass mac osx compass</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:169342ed1366/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:less"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:mac"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:osx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:compass"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://speakerdeck.com/u/imathis/p/sass-compass-the-future-of-stylesheets-now">
    <title>Sass &amp; Compass: The future of stylesheets now. // Speaker Deck</title>
    <dc:date>2011-11-11T23:46:55+00:00</dc:date>
    <link>http://speakerdeck.com/u/imathis/p/sass-compass-the-future-of-stylesheets-now</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Description

At The Future of Web Design I presented Sass and Compass. These were my slides yo.]]></description>
<dc:subject>compass css sass</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:d016262a882d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:compass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sonspring.com/journal/sass-for-designers">
    <title>Sass for Designers | SonSpring</title>
    <dc:date>2011-09-12T20:49:04+00:00</dc:date>
    <link>http://sonspring.com/journal/sass-for-designers</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[If you are anything like me, then as a designer you are also probably a bit of a curmudgeon, though perhaps you consider it perfectionism – and justifiably so. You have honed a specific workflow you adhere to because that is what works, dang it. Woe unto anyone who suggests you are not doing things in the best possible way, right? Yes, exactly! Except, well… no.

I believe my first reaction to Wynn Netherland, when he told me I ought to try Sass and that perhaps I would see a boost in productivity, was something along the lines of: “Bah, get off my lawn” — a reference to the cantankerous character played by Clint Eastwood in Gran Torino.

I came to realize that his suggestion was not a subtle way of saying “I know something you don’t know” (though he did), but more of a friendly nudge towards greater efficiency. He was just being a good neighbor, so to speak.

So, I am writing this post in an attempt to get designers out there (who are also already CSS savvy) to try Sass and Compass. I aim for this to be the article I wish I had read when I was first contemplating Sass but (at the time) did not consider it worthwhile. I could not have been more wrong.]]></description>
<dc:subject>css sass webdesign compass</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:a8777bbb70aa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:compass"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sass-lang.com/">
    <title>Sass - Syntactically Awesome Stylesheets</title>
    <dc:date>2011-01-04T15:45:52+00:00</dc:date>
    <link>http://sass-lang.com/</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[Sass makes CSS fun again. Sass is an extension of CSS3, 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 CSS3’s syntax. This means that every valid CSS3 stylesheet is valid SCSS as well. SCSS files use the extension .scss.]]></description>
<dc:subject>css sass scss</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:3a2ab68dd49e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:scss"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.zivtech.com/blog/css-suckers-introduction-sass-compass">
    <title>CSS is for Suckers. An Introduction to Sass &amp; Compass | Zivtech</title>
    <dc:date>2011-01-04T15:45:25+00:00</dc:date>
    <link>http://www.zivtech.com/blog/css-suckers-introduction-sass-compass</link>
    <dc:creator>Aetles</dc:creator><description><![CDATA[So you write a lot of CSS, right? I used to be like you. I'll bet you probably write enough CSS to see tons of possibilities in the code, but also maybe you pull your hair out over some of the limitations? It's ok, you can admit it. Like when you have to copy/paste code all over your stylesheets, or when you try to remember the browser prefixes and divergent syntaxes for CSS3 techniques, or how there's no help whatsoever in managing color values. Or maybe you're one of us super nerds who actually has a use for programmatic loops and logic? If you nodded for even one of those, then let me introduce you to Sass.]]></description>
<dc:subject>css sass scss</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:Aetles/b:2b5d7eccdde5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:Aetles/t:scss"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>