<?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: wp-content in Code is a Tell for Common WordPress Coding Mistakes</title>
	<atom:link href="http://foolswisdom.com/wp-content-in-code-common-mistakes/feed/" rel="self" type="application/rss+xml" />
	<link>http://foolswisdom.com/wp-content-in-code-common-mistakes/</link>
	<description>A fool and his blog are soon parted.</description>
	<lastBuildDate>Thu, 22 Jul 2010 01:55:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1-alpha</generator>
	<item>
		<title>By: Ted Szukalski</title>
		<link>http://foolswisdom.com/wp-content-in-code-common-mistakes/comment-page-1/#comment-231580</link>
		<dc:creator>Ted Szukalski</dc:creator>
		<pubDate>Tue, 14 Jul 2009 02:08:13 +0000</pubDate>
		<guid isPermaLink="false">http://foolswisdom.com/?p=1813#comment-231580</guid>
		<description>If you ask me it should simply be get_style(), which would output in a single HTTP response style.css from the current theme COMBINED with all en-queued CSS from plugins. This would save a lot of unnecessary HTTP request going back and forth for each CSS needed to render a page. You could also minify them on the fly with simple stripping code at the very least.</description>
		<content:encoded><![CDATA[<p>If you ask me it should simply be get_style(), which would output in a single HTTP response style.css from the current theme COMBINED with all en-queued CSS from plugins. This would save a lot of unnecessary HTTP request going back and forth for each CSS needed to render a page. You could also minify them on the fly with simple stripping code at the very least.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
