<?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: Linkage Etiquette (Part 1)</title>
	<atom:link href="http://www.devlounge.net/strategy/linkage-etiquette-part-1/feed" rel="self" type="application/rss+xml" />
	<link>http://www.devlounge.net/strategy/linkage-etiquette-part-1</link>
	<description>Design, Develop, and Grow</description>
	<lastBuildDate>Sat, 20 Mar 2010 15:15:39 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Eddie</title>
		<link>http://www.devlounge.net/strategy/linkage-etiquette-part-1/comment-page-1#comment-1304</link>
		<dc:creator>Eddie</dc:creator>
		<pubDate>Sun, 06 Aug 2006 20:31:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/news/linkage-etiquette-part-1#comment-1304</guid>
		<description>Glad ya&#039;ll enjoyed &quot;Part 1,&quot; which did have more of a &quot;copy&quot; feel to it. The next iteration will get into more of the design and hierarchy behind links (very important when you have a client who wants more than one &quot;CTA&quot;).

@Shalom: It would be superfluous if I hadn&#039;t already prefaced the link as needing a &quot;call to action.&quot; This is similar to your site, where you prompt users to &quot;view project,&quot; rather than simply stating &quot;project.&quot; Watch your type-os there, BTW.</description>
		<content:encoded><![CDATA[<p>Glad ya&#8217;ll enjoyed &#8220;Part 1,&#8221; which did have more of a &#8220;copy&#8221; feel to it. The next iteration will get into more of the design and hierarchy behind links (very important when you have a client who wants more than one &#8220;CTA&#8221;).</p>
<p>@Shalom: It would be superfluous if I hadn&#8217;t already prefaced the link as needing a &#8220;call to action.&#8221; This is similar to your site, where you prompt users to &#8220;view project,&#8221; rather than simply stating &#8220;project.&#8221; Watch your type-os there, BTW.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aj</title>
		<link>http://www.devlounge.net/strategy/linkage-etiquette-part-1/comment-page-1#comment-1298</link>
		<dc:creator>aj</dc:creator>
		<pubDate>Sun, 06 Aug 2006 12:08:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/news/linkage-etiquette-part-1#comment-1298</guid>
		<description>I&#039;m also looking forward to the next article :)</description>
		<content:encoded><![CDATA[<p>I&#8217;m also looking forward to the next article <img src='http://www.devlounge.net/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryce Roney</title>
		<link>http://www.devlounge.net/strategy/linkage-etiquette-part-1/comment-page-1#comment-1288</link>
		<dc:creator>Bryce Roney</dc:creator>
		<pubDate>Sat, 05 Aug 2006 08:44:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/news/linkage-etiquette-part-1#comment-1288</guid>
		<description>@Ronalfy: I agree, there are situations when _blank is and isn&#039;t appropriate.</description>
		<content:encoded><![CDATA[<p>@Ronalfy: I agree, there are situations when _blank is and isn&#8217;t appropriate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sholom Sandalow</title>
		<link>http://www.devlounge.net/strategy/linkage-etiquette-part-1/comment-page-1#comment-1277</link>
		<dc:creator>Sholom Sandalow</dc:creator>
		<pubDate>Fri, 04 Aug 2006 15:51:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/news/linkage-etiquette-part-1#comment-1277</guid>
		<description>Very informative.  You&#039;ve got some good rules of thumb in here.  However, I would remove the first two words of your first example link, so that the link simply says &#039;MOMA&#039;.  As you later point out, users know how the web works, so &#039;Check out&#039; is superfluous.</description>
		<content:encoded><![CDATA[<p>Very informative.  You&#8217;ve got some good rules of thumb in here.  However, I would remove the first two words of your first example link, so that the link simply says &#8216;MOMA&#8217;.  As you later point out, users know how the web works, so &#8216;Check out&#8217; is superfluous.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://www.devlounge.net/strategy/linkage-etiquette-part-1/comment-page-1#comment-1275</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Thu, 03 Aug 2006 23:01:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/news/linkage-etiquette-part-1#comment-1275</guid>
		<description>Always a great topic for a post -- as we still continually see these &quot;Click Here!&quot;s and &quot;This Link&quot;.  You brought up some key ideas that weren&#039;t mentioned in my article -- good write-up!</description>
		<content:encoded><![CDATA[<p>Always a great topic for a post &#8212; as we still continually see these &#8220;Click Here!&#8221;s and &#8220;This Link&#8221;.  You brought up some key ideas that weren&#8217;t mentioned in my article &#8212; good write-up!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronalfy</title>
		<link>http://www.devlounge.net/strategy/linkage-etiquette-part-1/comment-page-1#comment-1268</link>
		<dc:creator>Ronalfy</dc:creator>
		<pubDate>Thu, 03 Aug 2006 04:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.devlounge.net/news/linkage-etiquette-part-1#comment-1268</guid>
		<description>Great article.  Hopefully in Part 2 you&#039;ll go into pop-up windows, mystery meat, and link usability.</description>
		<content:encoded><![CDATA[<p>Great article.  Hopefully in Part 2 you&#8217;ll go into pop-up windows, mystery meat, and link usability.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
