<?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 Management on Large Sites</title>
	<atom:link href="http://www.defusion.org.uk/archives/2008/10/21/css-management-on-large-sites/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.defusion.org.uk/archives/2008/10/21/css-management-on-large-sites/</link>
	<description>I too will force my opinions on you</description>
	<lastBuildDate>Thu, 02 Feb 2012 16:16:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Lewis Litanzios</title>
		<link>http://www.defusion.org.uk/archives/2008/10/21/css-management-on-large-sites/comment-page-1/#comment-84056</link>
		<dc:creator>Lewis Litanzios</dc:creator>
		<pubDate>Sat, 31 Jan 2009 11:57:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.defusion.org.uk/archives/2008/10/21/css-management-on-large-sites/#comment-84056</guid>
		<description>I use PHP include()&#039;s with all my Javascript, perhaps I&#039;ll come round to your way of thinking with the CSS soon enough :P

Thanks for the compliments. Yea, it was [that] site (I started it in March 2008!), and the intricate CSS going on, that made &#039;CSS organisation&#039; big with me.

All the best, will speak soon no doubt. I&#039;m keeping Saturdays free for blogging, now I&#039;m single again :]</description>
		<content:encoded><![CDATA[<p>I use <acronym title="Hypertext PreProcessing">PHP</acronym> include()&#8217;s with all my Javascript, perhaps I&#8217;ll come round to your way of thinking with the <acronym title="Cascading Style Sheets">CSS</acronym> soon enough :P</p>
<p>Thanks for the compliments. Yea, it was [that] site (I started it in March 2008!), and the intricate <acronym title="Cascading Style Sheets">CSS</acronym> going on, that made &#8216;<acronym title="Cascading Style Sheets">CSS</acronym> organisation&#8217; big with me.</p>
<p>All the best, will speak soon no doubt. I&#8217;m keeping Saturdays free for blogging, now I&#8217;m single again :]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.defusion.org.uk/archives/2008/10/21/css-management-on-large-sites/comment-page-1/#comment-84053</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Sat, 31 Jan 2009 11:30:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.defusion.org.uk/archives/2008/10/21/css-management-on-large-sites/#comment-84053</guid>
		<description>Hi Lewis,

Yes CSS organisation can be a trade off between keeping things neatly organised and having only a handful of HTTP requests to get the CSS. When working on highly trafficked websites I think it is useful to optimise this by having either a build script or a server side script that combines your nicely encapsulated CSS files into a single CSS file to reduce the number of HTTP requests - as opening a new request actually has more overhead than you&#039;d think.

On a separate note, I just took a look at your site - loving the new design, especially your info bubbles and some of the hidden bits/easter eggs.

-D</description>
		<content:encoded><![CDATA[<p>Hi Lewis,</p>
<p>Yes <acronym title="Cascading Style Sheets">CSS</acronym> organisation can be a trade off between keeping things neatly organised and having only a handful of <acronym title="HyperText Transfer Protocol">HTTP</acronym> requests to get the <acronym title="Cascading Style Sheets">CSS</acronym>. When working on highly trafficked websites I think it is useful to optimise this by having either a build script or a server side script that combines your nicely encapsulated <acronym title="Cascading Style Sheets">CSS</acronym> files into a single <acronym title="Cascading Style Sheets">CSS</acronym> file to reduce the number of <acronym title="HyperText Transfer Protocol">HTTP</acronym> requests &#8211; as opening a new request actually has more overhead than you&#8217;d think.</p>
<p>On a separate note, I just took a look at your site &#8211; loving the new design, especially your info bubbles and some of the hidden bits/easter eggs.</p>
<p>-D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lewis Litanzios</title>
		<link>http://www.defusion.org.uk/archives/2008/10/21/css-management-on-large-sites/comment-page-1/#comment-84046</link>
		<dc:creator>Lewis Litanzios</dc:creator>
		<pubDate>Sat, 31 Jan 2009 09:54:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.defusion.org.uk/archives/2008/10/21/css-management-on-large-sites/#comment-84046</guid>
		<description>Hey Dave! Hope you&#039;re well. Just getting back to my blogs here, after a bit of a break.

CSS organisation has been big with me over the past few months. Take a look at this (http://tinyurl.com/cekzv5). I&#039;ve found, working on top of Andy Budd&#039;s suggestion of splitting your CSS into categories, that using indentation, rather like writing XHTML, is very helpful too.

@importing CSS is extremely useful, but I find having CSS in separate files is too long, and, rather like pulling in a lot of JS files, it&#039;s slower.

Hope that&#039;s useful.

PS. That first link is going *down* soon, as it&#039;s at a beta location ATM, so apologies if it doesn&#039;t work when you read this. It&#039;ll be live for the next week I would think anyway :]</description>
		<content:encoded><![CDATA[<p>Hey Dave! Hope you&#8217;re well. Just getting back to my blogs here, after a bit of a break.</p>
<p><acronym title="Cascading Style Sheets">CSS</acronym> organisation has been big with me over the past few months. Take a look at this (<a href="http://tinyurl.com/cekzv5" rel="nofollow">http://tinyurl.com/cekzv5</a>). I&#8217;ve found, working on top of Andy Budd&#8217;s suggestion of splitting your <acronym title="Cascading Style Sheets">CSS</acronym> into categories, that using indentation, rather like writing <acronym title="eXtensible HyperText Markup Language - HTML reformulated as XML">XHTML</acronym>, is very helpful too.</p>
<p>@importing <acronym title="Cascading Style Sheets">CSS</acronym> is extremely useful, but I find having <acronym title="Cascading Style Sheets">CSS</acronym> in separate files is too long, and, rather like pulling in a lot of JS files, it&#8217;s slower.</p>
<p>Hope that&#8217;s useful.</p>
<p>PS. That first link is going <strong>down</strong> soon, as it&#8217;s at a beta location ATM, so apologies if it doesn&#8217;t work when you read this. It&#8217;ll be live for the next week I would think anyway :]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michael</title>
		<link>http://www.defusion.org.uk/archives/2008/10/21/css-management-on-large-sites/comment-page-1/#comment-81540</link>
		<dc:creator>michael</dc:creator>
		<pubDate>Thu, 11 Dec 2008 11:57:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.defusion.org.uk/archives/2008/10/21/css-management-on-large-sites/#comment-81540</guid>
		<description>I always wondered where I picked up the habit of alphabetising my style rules =D I too have tried to replicate this css system a few times using plugins to analyse the current URI.</description>
		<content:encoded><![CDATA[<p>I always wondered where I picked up the habit of alphabetising my style rules =D I too have tried to replicate this <acronym title="Cascading Style Sheets">CSS</acronym> system a few times using plugins to analyse the current <acronym title="Uniform Resource Identifier">URI</acronym>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

