<?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>Paradox Designs &#187; CSS</title>
	<atom:link href="http://paradoxdgn.com/tags/css/feed" rel="self" type="application/rss+xml" />
	<link>http://paradoxdgn.com</link>
	<description>Blogging about technology, CSS, Html, and other things</description>
	<lastBuildDate>Fri, 23 Jul 2010 07:18:11 +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>How SASS made my site better</title>
		<link>http://paradoxdgn.com/post/how-sass-made-my-site-better</link>
		<comments>http://paradoxdgn.com/post/how-sass-made-my-site-better#comments</comments>
		<pubDate>Sat, 10 Jul 2010 18:06:45 +0000</pubDate>
		<dc:creator>Paradox</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[Web development]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[sass]]></category>
		<category><![CDATA[web design]]></category>

		<guid isPermaLink="false">http://paradoxdgn.com/?p=247</guid>
		<description><![CDATA[Sass, or Syntactically Awesome StyleSheets, is a CSS interpreter. It lets you use advanced programming features in your Stylesheets, such as conditionals, functions, math, and other things, to aid in writing large, complex stylesheets. Sass can help tremendously when writing both advanced (CSS3) stylesheets, and even basic projects. Using pre-existing css One of the benefits [...]]]></description>
		<wfw:commentRss>http://paradoxdgn.com/post/how-sass-made-my-site-better/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Flaws in the W3C&#8217;s working draft on print</title>
		<link>http://paradoxdgn.com/post/flaws-in-the-w3cs-working-draft-on-print</link>
		<comments>http://paradoxdgn.com/post/flaws-in-the-w3cs-working-draft-on-print#comments</comments>
		<pubDate>Tue, 02 Feb 2010 18:35:59 +0000</pubDate>
		<dc:creator>Paradox</dc:creator>
				<category><![CDATA[CSS]]></category>
		<category><![CDATA[css3]]></category>
		<category><![CDATA[page layout]]></category>
		<category><![CDATA[print]]></category>
		<category><![CDATA[working draft]]></category>

		<guid isPermaLink="false">http://www.paradoxdgn.com/?p=41</guid>
		<description><![CDATA[Recently, I designed a [[print stylesheet]] for this site. In doing so, I became quite friendly with the W3C&#8217;s stylesheet working draft. Most of this draft is well thought out, but here was one section that seemed very poorly drafted; the section on page-margin content. What are page margins? And why do they matter? Page [...]]]></description>
		<wfw:commentRss>http://paradoxdgn.com/post/flaws-in-the-w3cs-working-draft-on-print/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
