<?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: WPUnlimited 1.0.1 Released</title>
	<atom:link href="http://www.wpunlimited.com/news/wpunlimited-101-released/feed" rel="self" type="application/rss+xml" />
	<link>http://www.wpunlimited.com/news/wpunlimited-101-released</link>
	<description>Everything You Want to Know About WPUnlimited</description>
	<lastBuildDate>Tue, 12 May 2009 05:52:12 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Premium Theme Info</title>
		<link>http://www.wpunlimited.com/news/wpunlimited-101-released/comment-page-1#comment-58</link>
		<dc:creator>Premium Theme Info</dc:creator>
		<pubDate>Thu, 19 Mar 2009 19:42:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.wpunlimited.com/news/?p=39#comment-58</guid>
		<description>It&#039;s good to see the upgrade.</description>
		<content:encoded><![CDATA[<p>It&#8217;s good to see the upgrade.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.wpunlimited.com/news/wpunlimited-101-released/comment-page-1#comment-57</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 18 Mar 2009 19:55:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.wpunlimited.com/news/?p=39#comment-57</guid>
		<description>Like I mentioned in our twitter exchange, this has been duly noted, and will be addressed in a future version (probably 1.1 in a month or so), but overall it isn&#039;t very high on the overall priority list. 

I think features, true bug fixes, and tweaks to the UI are much more important than a lack of focus on fixing small validation errors that do little to effect the performance or display of the theme. I understand how some people feel about validating, but I am not really one of those people. In the end, it is nice to validate, but not mission critical. ;)</description>
		<content:encoded><![CDATA[<p>Like I mentioned in our twitter exchange, this has been duly noted, and will be addressed in a future version (probably 1.1 in a month or so), but overall it isn&#8217;t very high on the overall priority list. </p>
<p>I think features, true bug fixes, and tweaks to the UI are much more important than a lack of focus on fixing small validation errors that do little to effect the performance or display of the theme. I understand how some people feel about validating, but I am not really one of those people. In the end, it is nice to validate, but not mission critical. <img src='http://www.wpunlimited.com/news/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan Strawser</title>
		<link>http://www.wpunlimited.com/news/wpunlimited-101-released/comment-page-1#comment-49</link>
		<dc:creator>Bryan Strawser</dc:creator>
		<pubDate>Tue, 17 Mar 2009 04:52:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.wpunlimited.com/news/?p=39#comment-49</guid>
		<description>Can you do something about the CSS syntax errors and HTML standards errors?  When I was evaluating your theme I found 20+ CSS errors just by running it through the standard CSS validators -- with thesis (my current platform), I get 1 (which was my error).

Bryan</description>
		<content:encoded><![CDATA[<p>Can you do something about the CSS syntax errors and HTML standards errors?  When I was evaluating your theme I found 20+ CSS errors just by running it through the standard CSS validators &#8212; with thesis (my current platform), I get 1 (which was my error).</p>
<p>Bryan</p>
]]></content:encoded>
	</item>
</channel>
</rss>
