<?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>Moonpixel &#187; css</title>
	<atom:link href="http://moonpixel.com/category/blog/css/feed/" rel="self" type="application/rss+xml" />
	<link>http://moonpixel.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 20 Jul 2010 05:59:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>CSS / HTML Template &#8211; Download</title>
		<link>http://moonpixel.com/css-html-template-download/</link>
		<comments>http://moonpixel.com/css-html-template-download/#comments</comments>
		<pubDate>Sat, 22 May 2010 18:51:29 +0000</pubDate>
		<dc:creator>moonpixel</dc:creator>
				<category><![CDATA[css]]></category>
		<category><![CDATA[webdesign]]></category>
		<category><![CDATA[css framework]]></category>
		<category><![CDATA[css html template download]]></category>
		<category><![CDATA[css template]]></category>
		<category><![CDATA[css xhtml template download]]></category>

		<guid isPermaLink="false">http://moonpixel.com/?p=190</guid>
		<description><![CDATA[I have been using the 960 Grid System CSS Framework, 960px frame divided into 12 or 16 columns, as for the kind of websites I work on (large graphics, less text) the pixel based layout is suitable. After I did about 10-20 sites using this framework I started realising that the time it saves me when creating the layout, at the end of the day I spend extra when making tweaks to the site (and there always are tweaks) and I did revert back to using custom templates based on my specific needs. I did create a "website" template composed just from the very basic elements I keep using again and again. [...]]]></description>
		<wfw:commentRss>http://moonpixel.com/css-html-template-download/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Flexible CSS &#8211; Combining Classes vs Descendant Selectors</title>
		<link>http://moonpixel.com/flexible-css-combining-classes-vs-descendant-selectors/</link>
		<comments>http://moonpixel.com/flexible-css-combining-classes-vs-descendant-selectors/#comments</comments>
		<pubDate>Thu, 31 Dec 2009 08:55:20 +0000</pubDate>
		<dc:creator>moonpixel</dc:creator>
				<category><![CDATA[css]]></category>
		<category><![CDATA[css combining selectors]]></category>
		<category><![CDATA[descendant selectors]]></category>

		<guid isPermaLink="false">http://moonpixel.com/?p=79</guid>
		<description><![CDATA[Separating semantic and presentational code is a great idea, however sometimes it's worth not going 100% by the book.
For content like text and images I am finding, that a bit more HTML (XHTML) markup can save lots of time in the long run. 

XHTML which is short and sweet:
<pre lang="html4strict">
<div id="main-content">
<h1>Header <span>(some additional words)</span></h1> 
<p>Some text...</p>
<img src="..." />
<p>Some more text...</p>
</div>
</pre>]]></description>
		<wfw:commentRss>http://moonpixel.com/flexible-css-combining-classes-vs-descendant-selectors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
