<?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: How To Organize CSS Files?</title>
	<atom:link href="http://www.vanseodesign.com/css/how-to-organize-css-files/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vanseodesign.com/css/how-to-organize-css-files/</link>
	<description>Helping you build search engine friendly websites</description>
	<lastBuildDate>Tue, 27 Jul 2010 18:07:45 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Learn Web Design: Educational Resources for Beginners &#124; My Marketing University &#124; MyMarketingU.com</title>
		<link>http://www.vanseodesign.com/css/how-to-organize-css-files/comment-page-1/#comment-66318</link>
		<dc:creator>Learn Web Design: Educational Resources for Beginners &#124; My Marketing University &#124; MyMarketingU.com</dc:creator>
		<pubDate>Tue, 11 May 2010 15:46:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/blog/?p=643#comment-66318</guid>
		<description>[...] How to Organize CSS Files [...]</description>
		<content:encoded><![CDATA[<p>[...] How to Organize CSS Files [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Learn Web Design: Educational Resources for Beginners &#124; pro2go Designs Blog</title>
		<link>http://www.vanseodesign.com/css/how-to-organize-css-files/comment-page-1/#comment-63302</link>
		<dc:creator>Learn Web Design: Educational Resources for Beginners &#124; pro2go Designs Blog</dc:creator>
		<pubDate>Mon, 19 Apr 2010 23:53:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/blog/?p=643#comment-63302</guid>
		<description>[...] How to Organize CSS Files [...]</description>
		<content:encoded><![CDATA[<p>[...] How to Organize CSS Files [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Bradley</title>
		<link>http://www.vanseodesign.com/css/how-to-organize-css-files/comment-page-1/#comment-62442</link>
		<dc:creator>Steven Bradley</dc:creator>
		<pubDate>Mon, 12 Apr 2010 16:22:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/blog/?p=643#comment-62442</guid>
		<description>Seems like a good way to organize. The part that always gets me is something like font-family for comments. Say you decide the font for comments will be different than the rest of the page. Would you want to include the new font-family in typographic styles or in the specific section on comments?

I can see advantages to including it in either place.

I guess there&#039;s not going to be a perfect system of organization and the best thing to do is to be consistent.</description>
		<content:encoded><![CDATA[<p>Seems like a good way to organize. The part that always gets me is something like font-family for comments. Say you decide the font for comments will be different than the rest of the page. Would you want to include the new font-family in typographic styles or in the specific section on comments?</p>
<p>I can see advantages to including it in either place.</p>
<p>I guess there&#8217;s not going to be a perfect system of organization and the best thing to do is to be consistent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WebmistressM</title>
		<link>http://www.vanseodesign.com/css/how-to-organize-css-files/comment-page-1/#comment-61571</link>
		<dc:creator>WebmistressM</dc:creator>
		<pubDate>Mon, 05 Apr 2010 18:37:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/blog/?p=643#comment-61571</guid>
		<description>In the start, I never questioned organizing my CSS based on design.  I would always start my style.css like this:

/*
Theme Name:
Theme URI:
Description:
Version: 
Author: 
Author URI: 
Tags: 
*/
/* Table of Contents:
    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 seems like its a good working model as it is kind of a hybrid between the aspects you mention.  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.

Most widgets and plugins that have styling rules use a css file within the plugin/widget folder so you almost never need to add a #8.  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 start, I never questioned organizing my CSS based on design.  I would always start my style.css like this:</p>
<p>/*<br />
Theme Name:<br />
Theme URI:<br />
Description:<br />
Version:<br />
Author:<br />
Author URI:<br />
Tags:<br />
*/<br />
/* Table of Contents:<br />
    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)&#8211;NONE<br />
    6. Wordpress Calendar<br />
    7. WP-Specific Classes<br />
*/</p>
<p>It seems like its a good working model as it is kind of a hybrid between the aspects you mention.  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.</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 a #8.  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: Ali</title>
		<link>http://www.vanseodesign.com/css/how-to-organize-css-files/comment-page-1/#comment-27944</link>
		<dc:creator>Ali</dc:creator>
		<pubDate>Mon, 18 May 2009 15:48:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/blog/?p=643#comment-27944</guid>
		<description>Thank you for sharing this info..</description>
		<content:encoded><![CDATA[<p>Thank you for sharing this info..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Bradley</title>
		<link>http://www.vanseodesign.com/css/how-to-organize-css-files/comment-page-1/#comment-26775</link>
		<dc:creator>Steven Bradley</dc:creator>
		<pubDate>Tue, 05 May 2009 07:47:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/blog/?p=643#comment-26775</guid>
		<description>I usually leave everything in one css file too, though I may start using multiple css files for a project to make things easier to manage.</description>
		<content:encoded><![CDATA[<p>I usually leave everything in one css file too, though I may start using multiple css files for a project to make things easier to manage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan P</title>
		<link>http://www.vanseodesign.com/css/how-to-organize-css-files/comment-page-1/#comment-26768</link>
		<dc:creator>Bryan P</dc:creator>
		<pubDate>Tue, 05 May 2009 04:21:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/blog/?p=643#comment-26768</guid>
		<description>There have been times, I have even considered separating the CSS into different files.

I havent convinced myself this is a good practice, so I only think about it, when I am doing major changes to a site.</description>
		<content:encoded><![CDATA[<p>There have been times, I have even considered separating the CSS into different files.</p>
<p>I havent convinced myself this is a good practice, so I only think about it, when I am doing major changes to a site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Bradley</title>
		<link>http://www.vanseodesign.com/css/how-to-organize-css-files/comment-page-1/#comment-26621</link>
		<dc:creator>Steven Bradley</dc:creator>
		<pubDate>Sun, 03 May 2009 09:02:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/blog/?p=643#comment-26621</guid>
		<description>I think that&#039;s the better approach and it&#039;s about time I changed the way I organize my css. I&#039;m a creature of habit and haven&#039;t updated it awhile.

One thing I&#039;m still trying to work out is where to place certain css. Like the border property I mentioned. Should I pull out the color from the shortcut or just leave the entire border css together in one place. I&#039;ll go with my gut and adjust over time.

The webdeveloper toolbar is the one that gets the most use for me on Firefox. Lately I&#039;ve taken to using Safari more and I&#039;m having to use a different set of plugins. Sadly some I really like on FF have no Safari equivalent at the moment.</description>
		<content:encoded><![CDATA[<p>I think that&#8217;s the better approach and it&#8217;s about time I changed the way I organize my css. I&#8217;m a creature of habit and haven&#8217;t updated it awhile.</p>
<p>One thing I&#8217;m still trying to work out is where to place certain css. Like the border property I mentioned. Should I pull out the color from the shortcut or just leave the entire border css together in one place. I&#8217;ll go with my gut and adjust over time.</p>
<p>The webdeveloper toolbar is the one that gets the most use for me on Firefox. Lately I&#8217;ve taken to using Safari more and I&#8217;m having to use a different set of plugins. Sadly some I really like on FF have no Safari equivalent at the moment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan P</title>
		<link>http://www.vanseodesign.com/css/how-to-organize-css-files/comment-page-1/#comment-26493</link>
		<dc:creator>Bryan P</dc:creator>
		<pubDate>Fri, 01 May 2009 15:55:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.vanseodesign.com/blog/?p=643#comment-26493</guid>
		<description>I like organizing around design.  My files are generally have comment blocks which indicate whats in that area.  At the top I have a big block that &quot;indexes&quot; the css blocks.

If I need to change a font size, color, etc, I can get right to it without having to think, how is it structured on the page.

The webdeveloper plugin for Firefox, makes this even easier as it tells you the line that CSS element is on.</description>
		<content:encoded><![CDATA[<p>I like organizing around design.  My files are generally have comment blocks which indicate whats in that area.  At the top I have a big block that &#8220;indexes&#8221; the css blocks.</p>
<p>If I need to change a font size, color, etc, I can get right to it without having to think, how is it structured on the page.</p>
<p>The webdeveloper plugin for Firefox, makes this even easier as it tells you the line that CSS element is on.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
