<?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="http://breakpoint-sass.com/"/>
	<rdf:li rdf:resource="http://sassmeister.com/"/>
	<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:Seq>
    </items>
  </channel><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://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://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>
</rdf:RDF>