<?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: On Styling Links Within Content</title>
	<atom:link href="http://ephramzerb.com/2007/05/styling-links-content/feed/" rel="self" type="application/rss+xml" />
	<link>http://ephramzerb.com/2007/05/styling-links-content/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 02 Mar 2011 12:56:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: UtahLuxury.com</title>
		<link>http://ephramzerb.com/2007/05/styling-links-content/comment-page-1/#comment-21156</link>
		<dc:creator>UtahLuxury.com</dc:creator>
		<pubDate>Mon, 05 May 2008 02:37:53 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/05/styling-links-content/#comment-21156</guid>
		<description>I prefer to not stuff links into my content unless it is an internal link. That way there isn&#039;t any blurring of what is content and what is ad.</description>
		<content:encoded><![CDATA[<p>I prefer to not stuff links into my content unless it is an internal link. That way there isn&#8217;t any blurring of what is content and what is ad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ephram Zerb</title>
		<link>http://ephramzerb.com/2007/05/styling-links-content/comment-page-1/#comment-1121</link>
		<dc:creator>Ephram Zerb</dc:creator>
		<pubDate>Sun, 20 May 2007 01:00:14 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/05/styling-links-content/#comment-1121</guid>
		<description>@Erik:  There is definetly a tension, when using something like Google Adsense on your site, to make the ads consistent with the rest of your link treatments while also distinguishing the ads from your content.  On the one hand, ethics dictate that ads shouldn&#039;t be misinterpreted as your site&#039;s content.  On the other hand, a disparate treatment will likely make the ads less effective from the click-through perspective.

Super consistency in you link-treatments is a difficult thing to scale.  If you look at the Bookmarks that are featured on &lt;a href=&quot;http://www.ephramzerb.com&quot; rel=&quot;nofollow&quot;&gt;this site&#039;s homepage&lt;/a&gt; in the sidebar, you&#039;ll notice that the links are neither blue nor underlined.  Another example would be the navigation through the &lt;a href=&quot;http://www.nytimes.com&quot; rel=&quot;nofollow&quot;&gt;NYTimes.com&lt;/a&gt; property.  Maintaining an effective content-hierarchy drives decisions like this and the context that the positioning affords, makes them viable.

Most of the time, the positioning of the ads already communicates that the links and text are ad units.  If anything would make users stay away from those links, it would be just that.  The fact that there are certain inalienable properties that appear accross billions of google ads contributes to this effect as well.

I think you&#039;re right that a lot of designers would love the added control that you desire.  Unfortunately, when working with something so unmaleable it&#039;s an issue of compromise.  But encapsulating decions like this, with the help of context, can make them more manageable.</description>
		<content:encoded><![CDATA[<p>@Erik:  There is definetly a tension, when using something like Google Adsense on your site, to make the ads consistent with the rest of your link treatments while also distinguishing the ads from your content.  On the one hand, ethics dictate that ads shouldn&#8217;t be misinterpreted as your site&#8217;s content.  On the other hand, a disparate treatment will likely make the ads less effective from the click-through perspective.</p>
<p>Super consistency in you link-treatments is a difficult thing to scale.  If you look at the Bookmarks that are featured on <a href="http://www.ephramzerb.com" rel="nofollow">this site&#8217;s homepage</a> in the sidebar, you&#8217;ll notice that the links are neither blue nor underlined.  Another example would be the navigation through the <a href="http://www.nytimes.com" rel="nofollow">NYTimes.com</a> property.  Maintaining an effective content-hierarchy drives decisions like this and the context that the positioning affords, makes them viable.</p>
<p>Most of the time, the positioning of the ads already communicates that the links and text are ad units.  If anything would make users stay away from those links, it would be just that.  The fact that there are certain inalienable properties that appear accross billions of google ads contributes to this effect as well.</p>
<p>I think you&#8217;re right that a lot of designers would love the added control that you desire.  Unfortunately, when working with something so unmaleable it&#8217;s an issue of compromise.  But encapsulating decions like this, with the help of context, can make them more manageable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ephram Zerb</title>
		<link>http://ephramzerb.com/2007/05/styling-links-content/comment-page-1/#comment-1082</link>
		<dc:creator>Ephram Zerb</dc:creator>
		<pubDate>Tue, 15 May 2007 02:48:47 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/05/styling-links-content/#comment-1082</guid>
		<description>@Jonathan: Thanks for bringing up Paul Boag&#039;s comments.  He makes a good point and it&#039;s something to keep in mind when designing for mobile devices.  Equipped with this knowledge, this appears to be easily remedied by a mobile-specific stylesheet (this obviously necessitates browser support).  However, from a brief assessment it would appear that both Opera and IE mobile browsers appear to support &lt;code&gt;border-bottom&lt;/code&gt; without much difficulty (in context of inline links).

Paul Boag also notes that IE5 struggles with the &lt;code&gt;border-bottom&lt;/code&gt; property.  It&#039;s true, but trivial.  For one, the extent of the problem rests in the underline simply not showing up - the links still work and the main color remains. I have also made a conscious decision to not fully support an equivalent experience outside of the &lt;a href=&quot;http://developer.yahoo.com/yui/articles/gbs/index.html#gbschart&quot; rel=&quot;nofollow&quot;&gt;Grade-A browsers&lt;/a&gt;, making it all the less relevant for me. But I can comfortably say: ditching IE5 support is a safe bet for just about every new website project.

Btw, nice work on the Te Tuhi site.  Love the grid-based design, semantic HTML and strong colors.</description>
		<content:encoded><![CDATA[<p>@Jonathan: Thanks for bringing up Paul Boag&#8217;s comments.  He makes a good point and it&#8217;s something to keep in mind when designing for mobile devices.  Equipped with this knowledge, this appears to be easily remedied by a mobile-specific stylesheet (this obviously necessitates browser support).  However, from a brief assessment it would appear that both Opera and IE mobile browsers appear to support <code>border-bottom</code> without much difficulty (in context of inline links).</p>
<p>Paul Boag also notes that IE5 struggles with the <code>border-bottom</code> property.  It&#8217;s true, but trivial.  For one, the extent of the problem rests in the underline simply not showing up &#8211; the links still work and the main color remains. I have also made a conscious decision to not fully support an equivalent experience outside of the <a href="http://developer.yahoo.com/yui/articles/gbs/index.html#gbschart" rel="nofollow">Grade-A browsers</a>, making it all the less relevant for me. But I can comfortably say: ditching IE5 support is a safe bet for just about every new website project.</p>
<p>Btw, nice work on the Te Tuhi site.  Love the grid-based design, semantic HTML and strong colors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik</title>
		<link>http://ephramzerb.com/2007/05/styling-links-content/comment-page-1/#comment-1080</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Tue, 15 May 2007 02:20:06 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/05/styling-links-content/#comment-1080</guid>
		<description>One issue I wrestle with when designing an advertising-supported website is how to differentiate text ads from non-ad links.  This question is touched upon in the selected Simon Loxley quote: &lt;blockquote&gt;if it looks strange and unfamiliar, the reader won&#039;t go near it.&lt;/blockquote&gt;  Good design demands that users are not confused or tricked into clicking ads that look too much like main content, but text ads that appear &quot;strange and unfamiliar&quot; will probably receive fewer clicks.

Assuming that &lt;em&gt;some&lt;/em&gt; similarity between text ads and non-ad links is a good idea, constraints arise as long as advertisers demand control over the presentation of their ads (admittedly, a reasonable demand).  For example, Google currently allows website designers to customize the colors of AdSense for Content text ads, but does not allow customization of other CSS properties, including &lt;code&gt;font-family&lt;/code&gt;, &lt;code&gt;font-weight&lt;/code&gt;, &lt;code&gt;text-decoration&lt;/code&gt;, or &lt;code&gt;border-bottom&lt;/code&gt;.  This limits the website designer who wants to apply some of these properties to both text ads and non-ad links.</description>
		<content:encoded><![CDATA[<p>One issue I wrestle with when designing an advertising-supported website is how to differentiate text ads from non-ad links.  This question is touched upon in the selected Simon Loxley quote:<br />
<blockquote>if it looks strange and unfamiliar, the reader won&#8217;t go near it.</p></blockquote>
<p>  Good design demands that users are not confused or tricked into clicking ads that look too much like main content, but text ads that appear &#8220;strange and unfamiliar&#8221; will probably receive fewer clicks.</p>
<p>Assuming that <em>some</em> similarity between text ads and non-ad links is a good idea, constraints arise as long as advertisers demand control over the presentation of their ads (admittedly, a reasonable demand).  For example, Google currently allows website designers to customize the colors of AdSense for Content text ads, but does not allow customization of other CSS properties, including <code>font-family</code>, <code>font-weight</code>, <code>text-decoration</code>, or <code>border-bottom</code>.  This limits the website designer who wants to apply some of these properties to both text ads and non-ad links.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Nicol</title>
		<link>http://ephramzerb.com/2007/05/styling-links-content/comment-page-1/#comment-1051</link>
		<dc:creator>Jonathan Nicol</dc:creator>
		<pubDate>Sun, 13 May 2007 02:04:34 +0000</pubDate>
		<guid isPermaLink="false">http://ephramzerb.com/2007/05/styling-links-content/#comment-1051</guid>
		<description>An excellent addition to the topic!

You may be interested to know that my current approach to styling links is the same as the one you advocate. A few days back I launched a &lt;a href=&quot;http://tetuhi.org.nz/&quot; rel=&quot;nofollow&quot;&gt;client site&lt;/a&gt; using border-bottom on links instead of the traditional underline. I agree that a subtle underline is less disruptive to a pages&#039; visual design.

In his &lt;a href=&quot;http://www.thinkvitamin.com/features/design/dont-be-the-weakest-link&quot; rel=&quot;nofollow&quot;&gt;Vitamin article&lt;/a&gt; on the topic Paul Boag argues against messing with the underline at all due to poor support for border-bottom on certain devices, but I think he&#039;s in the minority on this one.</description>
		<content:encoded><![CDATA[<p>An excellent addition to the topic!</p>
<p>You may be interested to know that my current approach to styling links is the same as the one you advocate. A few days back I launched a <a href="http://tetuhi.org.nz/" rel="nofollow">client site</a> using border-bottom on links instead of the traditional underline. I agree that a subtle underline is less disruptive to a pages&#8217; visual design.</p>
<p>In his <a href="http://www.thinkvitamin.com/features/design/dont-be-the-weakest-link" rel="nofollow">Vitamin article</a> on the topic Paul Boag argues against messing with the underline at all due to poor support for border-bottom on certain devices, but I think he&#8217;s in the minority on this one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

