<?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: Insert Options &#8211; Individual Items, Standard Values or Rules</title>
	<atom:link href="http://sitecore.alexiasoft.nl/2010/02/01/insert-options-individual-items-standard-values-or-rules/feed/" rel="self" type="application/rss+xml" />
	<link>http://sitecore.alexiasoft.nl/2010/02/01/insert-options-individual-items-standard-values-or-rules/</link>
	<description>All about the web, online marketing, Sitecore, .NET and building sites...</description>
	<lastBuildDate>Tue, 31 Aug 2010 08:24:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Andy Pemberton</title>
		<link>http://sitecore.alexiasoft.nl/2010/02/01/insert-options-individual-items-standard-values-or-rules/comment-page-1/#comment-212569</link>
		<dc:creator>Andy Pemberton</dc:creator>
		<pubDate>Wed, 16 Jun 2010 03:43:33 +0000</pubDate>
		<guid isPermaLink="false">http://sitecore.alexiasoft.nl/2010/02/01/insert-options-individual-items-standard-values-or-rules/#comment-212569</guid>
		<description>Hey Alex:

Very good post; I had a different but closely related question I&#039;m curious for your opinion.

When assigning a layout and sublayouts to a given data template, there are a few options:

1. Individual items
- There are serious maintainability issues with this option, as content authors would be required to select all of the layout details for individual content items, so I&#039;d say this is a &#039;bad practice&#039;.

2. Data template
- Assigning the default layout and sublayouts on the data template allows individual items to inherit settings from the data template. 
- One downside of this option is that if a content author needs to change the layout/sublayouts on an individual item, they need to &quot;break&quot; the inheritance, resetting the layout details defined at the data template level (though the &#039;Copy To&#039; functionality on the Layout Details can make this easier).

3. Data template standard values
- Assigning the default layout/sublayouts on the data template&#039;s standard values allows invidual items to inherit settings from the data template, but will automatically &quot;break&quot; the inheritance. 
- This option has the benefit of already setting all of the layout details on individual items. On the other hand, this option could cause some maintainability issues because _all_ items will &quot;break&quot; inheritance from the parent template. One example is that it would be difficult to remove a sublayout from all items of a given data template type in this scenario.
	
So, what do you think? Is option 2 a &#039;95%&#039; best practice, where option 3 should be used for data templates that will most likely need to be reconfigured for each individual item?</description>
		<content:encoded><![CDATA[<p>Hey Alex:</p>
<p>Very good post; I had a different but closely related question I&#8217;m curious for your opinion.</p>
<p>When assigning a layout and sublayouts to a given data template, there are a few options:</p>
<p>1. Individual items<br />
- There are serious maintainability issues with this option, as content authors would be required to select all of the layout details for individual content items, so I&#8217;d say this is a &#8216;bad practice&#8217;.</p>
<p>2. Data template<br />
- Assigning the default layout and sublayouts on the data template allows individual items to inherit settings from the data template.<br />
- One downside of this option is that if a content author needs to change the layout/sublayouts on an individual item, they need to &#8220;break&#8221; the inheritance, resetting the layout details defined at the data template level (though the &#8216;Copy To&#8217; functionality on the Layout Details can make this easier).</p>
<p>3. Data template standard values<br />
- Assigning the default layout/sublayouts on the data template&#8217;s standard values allows invidual items to inherit settings from the data template, but will automatically &#8220;break&#8221; the inheritance.<br />
- This option has the benefit of already setting all of the layout details on individual items. On the other hand, this option could cause some maintainability issues because _all_ items will &#8220;break&#8221; inheritance from the parent template. One example is that it would be difficult to remove a sublayout from all items of a given data template type in this scenario.</p>
<p>So, what do you think? Is option 2 a &#8217;95%&#8217; best practice, where option 3 should be used for data templates that will most likely need to be reconfigured for each individual item?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lars Nielsen</title>
		<link>http://sitecore.alexiasoft.nl/2010/02/01/insert-options-individual-items-standard-values-or-rules/comment-page-1/#comment-199153</link>
		<dc:creator>Lars Nielsen</dc:creator>
		<pubDate>Wed, 03 Feb 2010 15:56:44 +0000</pubDate>
		<guid isPermaLink="false">http://sitecore.alexiasoft.nl/2010/02/01/insert-options-individual-items-standard-values-or-rules/#comment-199153</guid>
		<description>Nice to get it all assembled into one page... Thanks Alex</description>
		<content:encoded><![CDATA[<p>Nice to get it all assembled into one page&#8230; Thanks Alex</p>
]]></content:encoded>
	</item>
</channel>
</rss>
