<?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: CSS Tip #2: Structural Naming Convention in CSS</title>
	<atom:link href="http://sixrevisions.com/css/css-tips/css-tip-2-structural-naming-convention-in-css/feed/" rel="self" type="application/rss+xml" />
	<link>http://sixrevisions.com/css/css-tips/css-tip-2-structural-naming-convention-in-css/</link>
	<description></description>
	<lastBuildDate>Thu, 18 Mar 2010 03:49:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sidra Blue</title>
		<link>http://sixrevisions.com/css/css-tips/css-tip-2-structural-naming-convention-in-css/#comment-61082</link>
		<dc:creator>Sidra Blue</dc:creator>
		<pubDate>Thu, 04 Mar 2010 02:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=242#comment-61082</guid>
		<description>Good read, although personally, I hate long names that take up valuable filesize. With the way most websites are, you would want to reduce as much as possible, your filesizes that are being downloaded for a view.

There are the standard class names which would be common for all sites like #header, #footer, #content, but everything else is normally different these days.

Coming up with shorter but easily understandable names, (eg using ll in place of left, or rr in place of right, etc) and have an accompanying document on how these class names are so, would hopefully help Dave Newbie easily understand and help them &quot;immediately start work without having to constantly scratch their heads&quot;

Most would probably disagree though, but that&#039;s just our way =)</description>
		<content:encoded><![CDATA[<p>Good read, although personally, I hate long names that take up valuable filesize. With the way most websites are, you would want to reduce as much as possible, your filesizes that are being downloaded for a view.</p>
<p>There are the standard class names which would be common for all sites like #header, #footer, #content, but everything else is normally different these days.</p>
<p>Coming up with shorter but easily understandable names, (eg using ll in place of left, or rr in place of right, etc) and have an accompanying document on how these class names are so, would hopefully help Dave Newbie easily understand and help them &#8220;immediately start work without having to constantly scratch their heads&#8221;</p>
<p>Most would probably disagree though, but that&#8217;s just our way =)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Irene</title>
		<link>http://sixrevisions.com/css/css-tips/css-tip-2-structural-naming-convention-in-css/#comment-54420</link>
		<dc:creator>Irene</dc:creator>
		<pubDate>Wed, 16 Dec 2009 03:19:54 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=242#comment-54420</guid>
		<description>Thx,This is really useful for us.</description>
		<content:encoded><![CDATA[<p>Thx,This is really useful for us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dylan Bauer</title>
		<link>http://sixrevisions.com/css/css-tips/css-tip-2-structural-naming-convention-in-css/#comment-42490</link>
		<dc:creator>Dylan Bauer</dc:creator>
		<pubDate>Tue, 21 Jul 2009 08:55:14 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=242#comment-42490</guid>
		<description>Excellent read, I didn&#039;t even realize I was making some of these trivial mistakes!</description>
		<content:encoded><![CDATA[<p>Excellent read, I didn&#8217;t even realize I was making some of these trivial mistakes!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronald</title>
		<link>http://sixrevisions.com/css/css-tips/css-tip-2-structural-naming-convention-in-css/#comment-32789</link>
		<dc:creator>Ronald</dc:creator>
		<pubDate>Mon, 06 Apr 2009 03:51:38 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=242#comment-32789</guid>
		<description>this is really great post. I&#039;ll apply this when writing CSS such impart new knowledge on me...thanks for the share</description>
		<content:encoded><![CDATA[<p>this is really great post. I&#8217;ll apply this when writing CSS such impart new knowledge on me&#8230;thanks for the share</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sivas</title>
		<link>http://sixrevisions.com/css/css-tips/css-tip-2-structural-naming-convention-in-css/#comment-31373</link>
		<dc:creator>sivas</dc:creator>
		<pubDate>Sat, 21 Mar 2009 10:40:04 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=242#comment-31373</guid>
		<description>great, thank you</description>
		<content:encoded><![CDATA[<p>great, thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: amal</title>
		<link>http://sixrevisions.com/css/css-tips/css-tip-2-structural-naming-convention-in-css/#comment-23055</link>
		<dc:creator>amal</dc:creator>
		<pubDate>Mon, 15 Dec 2008 09:15:05 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=242#comment-23055</guid>
		<description>nice post. i always try to use structural naming.i think its more logical.</description>
		<content:encoded><![CDATA[<p>nice post. i always try to use structural naming.i think its more logical.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave</title>
		<link>http://sixrevisions.com/css/css-tips/css-tip-2-structural-naming-convention-in-css/#comment-22632</link>
		<dc:creator>dave</dc:creator>
		<pubDate>Thu, 11 Dec 2008 06:57:01 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=242#comment-22632</guid>
		<description>Yay for self-documenting code!</description>
		<content:encoded><![CDATA[<p>Yay for self-documenting code!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ivan acosta-rubio</title>
		<link>http://sixrevisions.com/css/css-tips/css-tip-2-structural-naming-convention-in-css/#comment-22607</link>
		<dc:creator>ivan acosta-rubio</dc:creator>
		<pubDate>Wed, 10 Dec 2008 23:30:45 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=242#comment-22607</guid>
		<description>Love the article!</description>
		<content:encoded><![CDATA[<p>Love the article!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Gube</title>
		<link>http://sixrevisions.com/css/css-tips/css-tip-2-structural-naming-convention-in-css/#comment-22527</link>
		<dc:creator>Jacob Gube</dc:creator>
		<pubDate>Tue, 09 Dec 2008 21:06:27 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=242#comment-22527</guid>
		<description>&lt;strong&gt;@Michael: &lt;/strong&gt; Yeah, exactly. I think for CSS, it&#039;s so simple that if you need to comment a lot, you may have to think about your code. For PHP, I do comment like there&#039;s no tomorrow though (I use the PEAR coding standards for my projects) - not only for people working on my stuff later on, but especially for my sake.

I&#039;m curious to hear more about how you break up your CSS files into the 3 sections you mentioned.</description>
		<content:encoded><![CDATA[<p><strong>@Michael: </strong> Yeah, exactly. I think for CSS, it&#8217;s so simple that if you need to comment a lot, you may have to think about your code. For PHP, I do comment like there&#8217;s no tomorrow though (I use the PEAR coding standards for my projects) &#8211; not only for people working on my stuff later on, but especially for my sake.</p>
<p>I&#8217;m curious to hear more about how you break up your CSS files into the 3 sections you mentioned.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://sixrevisions.com/css/css-tips/css-tip-2-structural-naming-convention-in-css/#comment-22457</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Tue, 09 Dec 2008 03:28:30 +0000</pubDate>
		<guid isPermaLink="false">http://sixrevisions.com/?p=242#comment-22457</guid>
		<description>@Jacob I agree, with CSS I don&#039;t do a whole lot of commenting, except for 1) Like you I comment things that may throw others off, and 2) I break my CSS files up into 3 sections (Standard Selectors, IDs and Classes) and use comments to differentiate the sections. Personal preference, but for me it makes it much easier to find what I&#039;m looking for.

Again, great article, I&#039;m looking forward to more.</description>
		<content:encoded><![CDATA[<p>@Jacob I agree, with CSS I don&#8217;t do a whole lot of commenting, except for 1) Like you I comment things that may throw others off, and 2) I break my CSS files up into 3 sections (Standard Selectors, IDs and Classes) and use comments to differentiate the sections. Personal preference, but for me it makes it much easier to find what I&#8217;m looking for.</p>
<p>Again, great article, I&#8217;m looking forward to more.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
