<?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: Redesigning the CS09 Default Site</title>
	<atom:link href="http://blog.kellyheard.com/redesigningthedefaultsite/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.kellyheard.com/redesigningthedefaultsite/</link>
	<description></description>
	<lastBuildDate>Fri, 25 Jun 2010 15:51:58 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Winson</title>
		<link>http://blog.kellyheard.com/redesigningthedefaultsite/comment-page-1/#comment-10</link>
		<dc:creator>Winson</dc:creator>
		<pubDate>Thu, 09 Apr 2009 17:13:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kellyheard.com/?p=272#comment-10</guid>
		<description>Great site Kelly. I will link to it!</description>
		<content:encoded><![CDATA[<p>Great site Kelly. I will link to it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly</title>
		<link>http://blog.kellyheard.com/redesigningthedefaultsite/comment-page-1/#comment-9</link>
		<dc:creator>Kelly</dc:creator>
		<pubDate>Thu, 09 Apr 2009 14:20:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kellyheard.com/?p=272#comment-9</guid>
		<description>You&#039;re correct!  This certainly isn&#039;t the best approach, but OK if you&#039;ve got one CS enabled site.  The best approach really is to build your own controls with the extensibility kit and deploy them as features on your sites.  This way you could affect controls differently for different sites.

Most controls are rendered using XSLT, where you could easily apply specific styles based on the subsite.  There were only a few that I needed to modify using the .ascx itself.</description>
		<content:encoded><![CDATA[<p>You&#8217;re correct!  This certainly isn&#8217;t the best approach, but OK if you&#8217;ve got one CS enabled site.  The best approach really is to build your own controls with the extensibility kit and deploy them as features on your sites.  This way you could affect controls differently for different sites.</p>
<p>Most controls are rendered using XSLT, where you could easily apply specific styles based on the subsite.  There were only a few that I needed to modify using the .ascx itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn Cicoria</title>
		<link>http://blog.kellyheard.com/redesigningthedefaultsite/comment-page-1/#comment-8</link>
		<dc:creator>Shawn Cicoria</dc:creator>
		<pubDate>Thu, 09 Apr 2009 13:43:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kellyheard.com/?p=272#comment-8</guid>
		<description>Have  you through through the fact that you&#039;ve impacted a farm level ControlTemplate and that ALL other sites on the Farm ultimately 

Clearly if you only have 1 style on a farm this is not an issue, but what&#039;s an approach if I want different storefronts, sites, etc. on the same Farm?  Is it all through XSLT and that&#039;s the only option other than custom code?</description>
		<content:encoded><![CDATA[<p>Have  you through through the fact that you&#8217;ve impacted a farm level ControlTemplate and that ALL other sites on the Farm ultimately </p>
<p>Clearly if you only have 1 style on a farm this is not an issue, but what&#8217;s an approach if I want different storefronts, sites, etc. on the same Farm?  Is it all through XSLT and that&#8217;s the only option other than custom code?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
