<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Simple Tips to Organise your CSS</title>
	<atom:link href="http://sixcrayons.com/2009/09/10/simple-tips-to-organise-your-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://sixcrayons.com/2009/09/10/simple-tips-to-organise-your-css/</link>
	<description>non-toxic designing</description>
	<lastBuildDate>Thu, 18 Nov 2010 14:55:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Branny</title>
		<link>http://sixcrayons.com/2009/09/10/simple-tips-to-organise-your-css/#comment-8</link>
		<dc:creator>Branny</dc:creator>
		<pubDate>Fri, 13 Nov 2009 16:37:33 +0000</pubDate>
		<guid isPermaLink="false">http://sixcrayons.com/?p=357#comment-8</guid>
		<description>I agree structuring your css is a big help when coming to maintenance tasks. A good structure can speed up maintenance dramatically.

I would say that too many calls to the server can slow your page load.  I prefer to keep everything in one stylesheet.  Print stylesheet should really be handled by the html, specifying the type print in the call to the css file.

A further step in naming conventions (a method I use) is to separate class and id&#039;s

so id&#039;s would follow
#ThisIsMyId
and classes
.this-is-my-class

This helps when using javascript to target items. especially when it comes to maintenance tasks.</description>
		<content:encoded><![CDATA[<p>I agree structuring your css is a big help when coming to maintenance tasks. A good structure can speed up maintenance dramatically.</p>
<p>I would say that too many calls to the server can slow your page load.  I prefer to keep everything in one stylesheet.  Print stylesheet should really be handled by the html, specifying the type print in the call to the css file.</p>
<p>A further step in naming conventions (a method I use) is to separate class and id&#8217;s</p>
<p>so id&#8217;s would follow<br />
#ThisIsMyId<br />
and classes<br />
.this-is-my-class</p>
<p>This helps when using javascript to target items. especially when it comes to maintenance tasks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

