<?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: You’re so not welcome.</title>
	<atom:link href="http://blog.braintraffic.com/2009/06/you%e2%80%99re-so-not-welcome/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.braintraffic.com/2009/06/you%e2%80%99re-so-not-welcome/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sat, 13 Mar 2010 06:35:13 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dave Buchanan</title>
		<link>http://blog.braintraffic.com/2009/06/you%e2%80%99re-so-not-welcome/comment-page-1/#comment-703</link>
		<dc:creator>Dave Buchanan</dc:creator>
		<pubDate>Thu, 13 Aug 2009 16:58:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=389#comment-703</guid>
		<description>Leaving &quot;Welcome&quot; out of web copy makes good sense.  I&#039;d extend that to the information that shows up when you bookmark a website.  The information that is saved with a bookmark is a valuable descriptor that is referred to whenever someone clicks on it in their saved bookmarks.  Saying &quot;Welcome to...&quot; or anything other than a short description of the page being bookmarked is nonessential information and a waste of valuable space.  It forces the user to erase the useless information and put in their own, a needless irritation.</description>
		<content:encoded><![CDATA[<p>Leaving &#8220;Welcome&#8221; out of web copy makes good sense.  I&#39;d extend that to the information that shows up when you bookmark a website.  The information that is saved with a bookmark is a valuable descriptor that is referred to whenever someone clicks on it in their saved bookmarks.  Saying &#8220;Welcome to&#8230;&#8221; or anything other than a short description of the page being bookmarked is nonessential information and a waste of valuable space.  It forces the user to erase the useless information and put in their own, a needless irritation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Buchanan</title>
		<link>http://blog.braintraffic.com/2009/06/you%e2%80%99re-so-not-welcome/comment-page-1/#comment-512</link>
		<dc:creator>Dave Buchanan</dc:creator>
		<pubDate>Thu, 13 Aug 2009 09:58:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=389#comment-512</guid>
		<description>Leaving &quot;Welcome&quot; out of web copy makes good sense.  I&#039;d extend that to the information that shows up when you bookmark a website.  The information that is saved with a bookmark is a valuable descriptor that is referred to whenever someone clicks on it in their saved bookmarks.  Saying &quot;Welcome to...&quot; or anything other than a short description of the page being bookmarked is nonessential information and a waste of valuable space.  It forces the user to erase the useless information and put in their own, a needless irritation.</description>
		<content:encoded><![CDATA[<p>Leaving &#8220;Welcome&#8221; out of web copy makes good sense.  I&#39;d extend that to the information that shows up when you bookmark a website.  The information that is saved with a bookmark is a valuable descriptor that is referred to whenever someone clicks on it in their saved bookmarks.  Saying &#8220;Welcome to&#8230;&#8221; or anything other than a short description of the page being bookmarked is nonessential information and a waste of valuable space.  It forces the user to erase the useless information and put in their own, a needless irritation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wendy</title>
		<link>http://blog.braintraffic.com/2009/06/you%e2%80%99re-so-not-welcome/comment-page-1/#comment-458</link>
		<dc:creator>Wendy</dc:creator>
		<pubDate>Tue, 09 Jun 2009 02:26:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=389#comment-458</guid>
		<description>Brilliant. Agree completely. Now can someone please build a website that waves at me from across the room and offers me cake; I&#039;ve forgotten my lunch.</description>
		<content:encoded><![CDATA[<p>Brilliant. Agree completely. Now can someone please build a website that waves at me from across the room and offers me cake; I&#39;ve forgotten my lunch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LoneWebber</title>
		<link>http://blog.braintraffic.com/2009/06/you%e2%80%99re-so-not-welcome/comment-page-1/#comment-456</link>
		<dc:creator>LoneWebber</dc:creator>
		<pubDate>Wed, 03 Jun 2009 17:30:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=389#comment-456</guid>
		<description>Q: Does this &quot;don&#039;t welcome&quot; rule apply to personal/individual&#039;s websites or social organizations instead of for-profit entities? How do you &quot;show&quot; that the page is the &quot;entrance&quot; to information about me/us?</description>
		<content:encoded><![CDATA[<p>Q: Does this &#8220;don&#39;t welcome&#8221; rule apply to personal/individual&#39;s websites or social organizations instead of for-profit entities? How do you &#8220;show&#8221; that the page is the &#8220;entrance&#8221; to information about me/us?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: theredheadsaid</title>
		<link>http://blog.braintraffic.com/2009/06/you%e2%80%99re-so-not-welcome/comment-page-1/#comment-455</link>
		<dc:creator>theredheadsaid</dc:creator>
		<pubDate>Wed, 03 Jun 2009 17:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=389#comment-455</guid>
		<description>Welcome messages are from a time when people weren&#039;t sure what websites were all about. I agree though : if your web copy is clear and design is intuitive, users will be able to know why they are there and what they should do next. &lt;br&gt;&lt;br&gt;**But why, oh why, are there still people who on their voice mail, tell me the mechanics of how to leave a message?</description>
		<content:encoded><![CDATA[<p>Welcome messages are from a time when people weren&#39;t sure what websites were all about. I agree though : if your web copy is clear and design is intuitive, users will be able to know why they are there and what they should do next. </p>
<p>**But why, oh why, are there still people who on their voice mail, tell me the mechanics of how to leave a message?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tariq</title>
		<link>http://blog.braintraffic.com/2009/06/you%e2%80%99re-so-not-welcome/comment-page-1/#comment-453</link>
		<dc:creator>Tariq</dc:creator>
		<pubDate>Mon, 01 Jun 2009 16:22:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.braintraffic.com/?p=389#comment-453</guid>
		<description>Gerry McGovern would also suggest that titles and descriptions of the content that &quot;you&#039;re about to see&quot; should be descriptive in nature, not &quot;smart&quot; or catchy. That way, the user has a better idea of whether or not it is worth their time to check out the article/post/page. If you over-deliver the product (like the Yahoo main page does every day), then you disappoint your users and they won&#039;t come back. If your titles/descriptions are too vague or not descriptive enough, then you won&#039;t get the user in the first place. I would suggest that the title of this post fits the latter category. That said, if you can manage to both be descriptive and catchy/&quot;smart&quot;, then score for you! Great post content though! It is immensely annoying when web sites provide no real actionable content and instead fill their pages with &quot;welcoming platitudes&quot;. Kudos for spreading the word and trying to make the world more web usable/readable!</description>
		<content:encoded><![CDATA[<p>Gerry McGovern would also suggest that titles and descriptions of the content that &#8220;you&#39;re about to see&#8221; should be descriptive in nature, not &#8220;smart&#8221; or catchy. That way, the user has a better idea of whether or not it is worth their time to check out the article/post/page. If you over-deliver the product (like the Yahoo main page does every day), then you disappoint your users and they won&#39;t come back. If your titles/descriptions are too vague or not descriptive enough, then you won&#39;t get the user in the first place. I would suggest that the title of this post fits the latter category. That said, if you can manage to both be descriptive and catchy/&#8221;smart&#8221;, then score for you! Great post content though! It is immensely annoying when web sites provide no real actionable content and instead fill their pages with &#8220;welcoming platitudes&#8221;. Kudos for spreading the word and trying to make the world more web usable/readable!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
