<?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 Organizing Your CSS Files</title>
	<atom:link href="http://fwebde.com/css/tips-for-organizing-css-files/feed/" rel="self" type="application/rss+xml" />
	<link>http://fwebde.com/css/tips-for-organizing-css-files/</link>
	<description>Helping people to make fantastic websites, whether you are a designer, a developer, or someone just who loves websites.</description>
	<lastBuildDate>Sun, 05 Sep 2010 13:54:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: WebmistressM</title>
		<link>http://fwebde.com/css/tips-for-organizing-css-files/comment-page-1/#comment-1443</link>
		<dc:creator>WebmistressM</dc:creator>
		<pubDate>Mon, 05 Apr 2010 18:45:14 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=588#comment-1443</guid>
		<description>In the case of Wordpress, I have this method of organization:


1. Base Font, Text &amp; Colors
2. Layout
3. Post/Page Content
4. Comment/Pingback Properties
5. Search Bar/Box Properties (optional)–NONE
6. Wordpress Calendar
7. WP-Specific Classes

It was my attempt at being a hybrid between pure style organization by html structure, and structuring it around design aspects.  The way I see it, you will always have div IDs for each area of the site. The calendar function that wordpress provides is optional, so you dont always need 6 or 7, but it is easy to remove if that is the case.

Most widgets and plugins that have styling rules use a css file within the plugin/widget folder so you almost never need to add anything more. Either way, this organization has helped me in knowing all the kinds of styling I might need for wordpress but they are organized in such a way that I can abstain from including areas I dont need in a specific theme such as the wordpress calendar styling.</description>
		<content:encoded><![CDATA[<p>In the case of WordPress, I have this method of organization:</p>
<p>1. Base Font, Text &amp; Colors<br />
2. Layout<br />
3. Post/Page Content<br />
4. Comment/Pingback Properties<br />
5. Search Bar/Box Properties (optional)–NONE<br />
6. WordPress Calendar<br />
7. WP-Specific Classes</p>
<p>It was my attempt at being a hybrid between pure style organization by html structure, and structuring it around design aspects.  The way I see it, you will always have div IDs for each area of the site. The calendar function that wordpress provides is optional, so you dont always need 6 or 7, but it is easy to remove if that is the case.</p>
<p>Most widgets and plugins that have styling rules use a css file within the plugin/widget folder so you almost never need to add anything more. Either way, this organization has helped me in knowing all the kinds of styling I might need for wordpress but they are organized in such a way that I can abstain from including areas I dont need in a specific theme such as the wordpress calendar styling.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Armine</title>
		<link>http://fwebde.com/css/tips-for-organizing-css-files/comment-page-1/#comment-418</link>
		<dc:creator>Armine</dc:creator>
		<pubDate>Thu, 12 Nov 2009 14:47:20 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=588#comment-418</guid>
		<description>Thank you for this list!</description>
		<content:encoded><![CDATA[<p>Thank you for this list!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Bannatyne</title>
		<link>http://fwebde.com/css/tips-for-organizing-css-files/comment-page-1/#comment-383</link>
		<dc:creator>Eric Bannatyne</dc:creator>
		<pubDate>Sat, 24 Oct 2009 16:19:18 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=588#comment-383</guid>
		<description>@Pieter: I must have missed something when checking the post. Thanks for pointing that out!</description>
		<content:encoded><![CDATA[<p>@Pieter: I must have missed something when checking the post. Thanks for pointing that out!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pieter</title>
		<link>http://fwebde.com/css/tips-for-organizing-css-files/comment-page-1/#comment-381</link>
		<dc:creator>Pieter</dc:creator>
		<pubDate>Sat, 24 Oct 2009 09:20:14 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=588#comment-381</guid>
		<description>Hmm, I think you&#039;ve got something wrong with the shorthands.

You say: &quot;If there are only two values, it is assumed to be top and bottom.&quot;

This is actually assumed to be top/bottom and left/right.
margin: 5px
-&gt; T/R/B/L: 5px

margin: 5px 10px
-&gt; T/B: 5px  - R/L: 10px;

margin: 5px 10px 15px
-&gt; T: 5px - R/L: 10px - B: 15px

That&#039;s how shorthand is used.
Nice article :)

Pieter.</description>
		<content:encoded><![CDATA[<p>Hmm, I think you've got something wrong with the shorthands.</p>
<p>You say: "If there are only two values, it is assumed to be top and bottom."</p>
<p>This is actually assumed to be top/bottom and left/right.<br />
margin: 5px<br />
-&gt; T/R/B/L: 5px</p>
<p>margin: 5px 10px<br />
-&gt; T/B: 5px  - R/L: 10px;</p>
<p>margin: 5px 10px 15px<br />
-&gt; T: 5px - R/L: 10px - B: 15px</p>
<p>That's how shorthand is used.<br />
Nice article :)</p>
<p>Pieter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Bannatyne</title>
		<link>http://fwebde.com/css/tips-for-organizing-css-files/comment-page-1/#comment-368</link>
		<dc:creator>Eric Bannatyne</dc:creator>
		<pubDate>Fri, 16 Oct 2009 21:46:53 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=588#comment-368</guid>
		<description>@André: I forgot to mention, I use the &lt;a href=&quot;http://www.cssdrive.com/index.php/main/csscompressor/&quot;&gt;CSS Drive Compressor&lt;/a&gt; to compress my CSS. I just manually go and put my files together before compressing it.

Thanks for reminding me</description>
		<content:encoded><![CDATA[<p>@André: I forgot to mention, I use the <a href="http://www.cssdrive.com/index.php/main/csscompressor/">CSS Drive Compressor</a> to compress my CSS. I just manually go and put my files together before compressing it.</p>
<p>Thanks for reminding me</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: André</title>
		<link>http://fwebde.com/css/tips-for-organizing-css-files/comment-page-1/#comment-366</link>
		<dc:creator>André</dc:creator>
		<pubDate>Fri, 16 Oct 2009 16:32:26 +0000</pubDate>
		<guid isPermaLink="false">http://fwebde.com/?p=588#comment-366</guid>
		<description>Hi Eric.

It&#039;s Andre from Brazil. Those are nice tips, but do you use any kind of tool to join and compress the CSS files?

Thanks!</description>
		<content:encoded><![CDATA[<p>Hi Eric.</p>
<p>It's Andre from Brazil. Those are nice tips, but do you use any kind of tool to join and compress the CSS files?</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
