<?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: Tips for Coding Better CSS &#8211; Part I</title>
	<atom:link href="http://designadaptations.com/design/tips-for-coding-better-css-part-i/feed/" rel="self" type="application/rss+xml" />
	<link>http://designadaptations.com/design/tips-for-coding-better-css-part-i/</link>
	<description></description>
	<lastBuildDate>Sun, 02 Aug 2009 05:47:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike</title>
		<link>http://designadaptations.com/design/tips-for-coding-better-css-part-i/comment-page-1/#comment-3318</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Mon, 06 Apr 2009 21:55:53 +0000</pubDate>
		<guid isPermaLink="false">http://designadaptations.com/notebook/tips-for-coding-better-css-part-i/#comment-3318</guid>
		<description>Wow, great tips. I&#039;m going on to the next article now. I especially like the global *. I didn&#039;t know about that, but I think that would save a lot of pain. Thanks!</description>
		<content:encoded><![CDATA[<p>Wow, great tips. I&#8217;m going on to the next article now. I especially like the global *. I didn&#8217;t know about that, but I think that would save a lot of pain. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tips For Coding Better CSS - Part II &#124; Design Adaptations</title>
		<link>http://designadaptations.com/design/tips-for-coding-better-css-part-i/comment-page-1/#comment-179</link>
		<dc:creator>Tips For Coding Better CSS - Part II &#124; Design Adaptations</dc:creator>
		<pubDate>Mon, 21 May 2007 15:46:18 +0000</pubDate>
		<guid isPermaLink="false">http://designadaptations.com/notebook/tips-for-coding-better-css-part-i/#comment-179</guid>
		<description>[...] week, in Part I of this set, I talked about small but significant ways to optimize your CSS. In this article I suggest some methods for keeping your CSS organized. While some of the tips here [...]</description>
		<content:encoded><![CDATA[<p>[...] week, in Part I of this set, I talked about small but significant ways to optimize your CSS. In this article I suggest some methods for keeping your CSS organized. While some of the tips here [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charity</title>
		<link>http://designadaptations.com/design/tips-for-coding-better-css-part-i/comment-page-1/#comment-178</link>
		<dc:creator>Charity</dc:creator>
		<pubDate>Sat, 19 May 2007 16:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://designadaptations.com/notebook/tips-for-coding-better-css-part-i/#comment-178</guid>
		<description>Sure Tara! Every little bit helps right? ;)</description>
		<content:encoded><![CDATA[<p>Sure Tara! Every little bit helps right? ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tara</title>
		<link>http://designadaptations.com/design/tips-for-coding-better-css-part-i/comment-page-1/#comment-177</link>
		<dc:creator>Tara</dc:creator>
		<pubDate>Sat, 19 May 2007 08:04:01 +0000</pubDate>
		<guid isPermaLink="false">http://designadaptations.com/notebook/tips-for-coding-better-css-part-i/#comment-177</guid>
		<description>Love your tip about how to remember top right bottom left (see I remember already!) I was wondering how I  would get that to stay in my head. Thanks</description>
		<content:encoded><![CDATA[<p>Love your tip about how to remember top right bottom left (see I remember already!) I was wondering how I  would get that to stay in my head. Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quick and Easy Tools For Optimizing Your CSS &#124; Design Adaptations</title>
		<link>http://designadaptations.com/design/tips-for-coding-better-css-part-i/comment-page-1/#comment-176</link>
		<dc:creator>Quick and Easy Tools For Optimizing Your CSS &#124; Design Adaptations</dc:creator>
		<pubDate>Fri, 18 May 2007 23:59:33 +0000</pubDate>
		<guid isPermaLink="false">http://designadaptations.com/notebook/tips-for-coding-better-css-part-i/#comment-176</guid>
		<description>[...] you read my article on tips for optimizing your stylesheets, you may already be putting some of those things into practice. Here then, are a few nifty (and [...]</description>
		<content:encoded><![CDATA[<p>[...] you read my article on tips for optimizing your stylesheets, you may already be putting some of those things into practice. Here then, are a few nifty (and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charity</title>
		<link>http://designadaptations.com/design/tips-for-coding-better-css-part-i/comment-page-1/#comment-175</link>
		<dc:creator>Charity</dc:creator>
		<pubDate>Fri, 18 May 2007 14:03:58 +0000</pubDate>
		<guid isPermaLink="false">http://designadaptations.com/notebook/tips-for-coding-better-css-part-i/#comment-175</guid>
		<description>What do you know, I&#039;m in the same situation! I can&#039;t find the original source where I read that tip. I thought it was something I saw long ago in one of my CSS books, but now I can&#039;t be sure. If you ever remember where that article was, please drop me a line. I&#039;d be curious to read it.</description>
		<content:encoded><![CDATA[<p>What do you know, I&#8217;m in the same situation! I can&#8217;t find the original source where I read that tip. I thought it was something I saw long ago in one of my CSS books, but now I can&#8217;t be sure. If you ever remember where that article was, please drop me a line. I&#8217;d be curious to read it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Enderson</title>
		<link>http://designadaptations.com/design/tips-for-coding-better-css-part-i/comment-page-1/#comment-174</link>
		<dc:creator>Paul Enderson</dc:creator>
		<pubDate>Fri, 18 May 2007 10:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://designadaptations.com/notebook/tips-for-coding-better-css-part-i/#comment-174</guid>
		<description>OK. I get that now you&#039;ve pointed it out! I do remember reading a while ago, an article that said that measurement type *should* always be specified...

I can&#039;t find it now (of course), but I have a funny feeling that it was something to do how browsers make use of CSS when printing a page. I wish I&#039;d bookmarked it!</description>
		<content:encoded><![CDATA[<p>OK. I get that now you&#8217;ve pointed it out! I do remember reading a while ago, an article that said that measurement type *should* always be specified&#8230;</p>
<p>I can&#8217;t find it now (of course), but I have a funny feeling that it was something to do how browsers make use of CSS when printing a page. I wish I&#8217;d bookmarked it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charity</title>
		<link>http://designadaptations.com/design/tips-for-coding-better-css-part-i/comment-page-1/#comment-173</link>
		<dc:creator>Charity</dc:creator>
		<pubDate>Fri, 18 May 2007 02:35:32 +0000</pubDate>
		<guid isPermaLink="false">http://designadaptations.com/notebook/tips-for-coding-better-css-part-i/#comment-173</guid>
		<description>You&#039;re right Paul! Specifying 0 is common and often necessary, and I see now that maybe I wasn&#039;t very clear on that first tip. I was trying to suggest that a &lt;em&gt;unit&lt;/em&gt; of measurement &lt;em&gt;with&lt;/em&gt; 0 is unnecessary. So declaring {margin:0PX;} only needs to be declared as {margin:0;}. Does that makes sense? If you take another gander at the code you linked, you&#039;ll notice there&#039;s no specific unit attached to any of the zero values - they&#039;re just zero. :) Sorry if that was confusing.</description>
		<content:encoded><![CDATA[<p>You&#8217;re right Paul! Specifying 0 is common and often necessary, and I see now that maybe I wasn&#8217;t very clear on that first tip. I was trying to suggest that a <em>unit</em> of measurement <em>with</em> 0 is unnecessary. So declaring {margin:0PX;} only needs to be declared as {margin:0;}. Does that makes sense? If you take another gander at the code you linked, you&#8217;ll notice there&#8217;s no specific unit attached to any of the zero values &#8211; they&#8217;re just zero. :) Sorry if that was confusing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Enderson</title>
		<link>http://designadaptations.com/design/tips-for-coding-better-css-part-i/comment-page-1/#comment-172</link>
		<dc:creator>Paul Enderson</dc:creator>
		<pubDate>Fri, 18 May 2007 02:12:26 +0000</pubDate>
		<guid isPermaLink="false">http://designadaptations.com/notebook/tips-for-coding-better-css-part-i/#comment-172</guid>
		<description>Actually, sometimes there is a valid reason to specify a zero value - if it&#039;s to reset a particular browser&#039;s styling.

See this for more info: http://developer.yahoo.com/yui/reset</description>
		<content:encoded><![CDATA[<p>Actually, sometimes there is a valid reason to specify a zero value &#8211; if it&#8217;s to reset a particular browser&#8217;s styling.</p>
<p>See this for more info: <a href="http://developer.yahoo.com/yui/reset" rel="nofollow">http://developer.yahoo.com/yui/reset</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
