<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Benton Barnett &#187; Ruby</title>
	<atom:link href="http://blog.bentonbarnett.com/category/programming/ruby/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.bentonbarnett.com</link>
	<description>Things I find interesting, and some things I don&#039;t.</description>
	<lastBuildDate>Fri, 09 Jul 2010 18:39:51 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Using HAML and SASS on a backend that supports neither</title>
		<link>http://blog.bentonbarnett.com/30/using-haml-and-sass-on-a-backend-that-supports-neither/</link>
		<comments>http://blog.bentonbarnett.com/30/using-haml-and-sass-on-a-backend-that-supports-neither/#comments</comments>
		<pubDate>Wed, 11 Mar 2009 20:50:52 +0000</pubDate>
		<dc:creator>Benton Barnett</dc:creator>
				<category><![CDATA[Ruby]]></category>

		<guid isPermaLink="false">http://www.bentonbarnett.com/?p=30</guid>
		<description><![CDATA[Thomas Reynolds on the difficulties using HAML and SASS when dealing with a backend that supports neither: Sass makes me a faster in my initial development, but it also speeds up tweaking small site-wide issues and overall maintenance. I develop my Sass modularly and try to use variables for site-wide colors, border and fonts. Wouldn’t [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://awardwinningfjords.com/">Thomas Reynolds</a> on the difficulties using HAML and SASS when dealing with a backend that supports neither:</p>
<blockquote><p>Sass makes me a faster in my initial development, but it also speeds up tweaking small site-wide issues and overall maintenance. I develop my Sass modularly and try to use variables for site-wide colors, border and fonts. Wouldn’t it be great if I could use Sass throughout the entire development cycle?  <a href="http://awardwinningfjords.com/2009/03/11/compass-the-future-of-sass-development/">More&#8230;</a></p></blockquote>
<p>Thomas goes on to suggest <a href="http://acts-as-architect.blogspot.com/2008/11/introducing-compass.html">Compass</a>, a unique set of tools that has translated common CSS libraries to SASS but also compiles SASS to CSS on the fly.</p>
<p>I&#8217;ve only just started working in HAML and SASS but I can already think of a few projects that would benefit from <a href="http://github.com/chriseppstein">Chris Eppstein&#8217;s work</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.bentonbarnett.com/30/using-haml-and-sass-on-a-backend-that-supports-neither/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
