<?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: Admin and End User Naming Conventions</title>
	<atom:link href="http://corypeters.net/2009/06/admin-and-end-user-naming-conventions/feed/" rel="self" type="application/rss+xml" />
	<link>http://corypeters.net/2009/06/admin-and-end-user-naming-conventions/</link>
	<description>Adventures with SharePoint</description>
	<lastBuildDate>Fri, 27 Jan 2012 02:06:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Cory</title>
		<link>http://corypeters.net/2009/06/admin-and-end-user-naming-conventions/comment-page-1/#comment-122</link>
		<dc:creator>Cory</dc:creator>
		<pubDate>Wed, 06 Oct 2010 00:15:40 +0000</pubDate>
		<guid isPermaLink="false">http://corypeters.net/?p=153#comment-122</guid>
		<description>Hey Kevin,

Thanks for the comment! If you are referring to web part headers then I think the key is the content that is inside of the web part. Try to ensure that the web part header describes BOTH the content AND how the content is filtered / sorted.

So let&#039;s use your example of a training calendar. I could have a web part that is filtered to show events that have not expired and sorted with the soonest at the top. In this case I would call my web part &quot;Upcoming Events&quot;. I will also use this practice on views for libraries and lists as well. &quot;My Documents&quot;, &quot;Word Documents&quot;, &quot;Expired Announcements&quot;, etc.

Thanks again for the question!</description>
		<content:encoded><![CDATA[<p>Hey Kevin,</p>
<p>Thanks for the comment! If you are referring to web part headers then I think the key is the content that is inside of the web part. Try to ensure that the web part header describes BOTH the content AND how the content is filtered / sorted.</p>
<p>So let&#8217;s use your example of a training calendar. I could have a web part that is filtered to show events that have not expired and sorted with the soonest at the top. In this case I would call my web part &#8220;Upcoming Events&#8221;. I will also use this practice on views for libraries and lists as well. &#8220;My Documents&#8221;, &#8220;Word Documents&#8221;, &#8220;Expired Announcements&#8221;, etc.</p>
<p>Thanks again for the question!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kevin</title>
		<link>http://corypeters.net/2009/06/admin-and-end-user-naming-conventions/comment-page-1/#comment-121</link>
		<dc:creator>kevin</dc:creator>
		<pubDate>Tue, 05 Oct 2010 17:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://corypeters.net/?p=153#comment-121</guid>
		<description>What about Web parts from an end user perspective. 

Example:  If I add a calendar web parts maybe. Training Calender. 

It might not matter. thx.</description>
		<content:encoded><![CDATA[<p>What about Web parts from an end user perspective. </p>
<p>Example:  If I add a calendar web parts maybe. Training Calender. </p>
<p>It might not matter. thx.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

