<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>AlbGeek.com &#187; web email</title>
	<atom:link href="http://albgeek.com/tag/web-email/feed/" rel="self" type="application/rss+xml" />
	<link>http://albgeek.com</link>
	<description>Never let a computer know you&#039;re in a hurry!</description>
	<lastBuildDate>Tue, 22 May 2012 17:25:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>9 best practices for email design</title>
		<link>http://albgeek.com/2008/03/9-best-practices-for-email-design/</link>
		<comments>http://albgeek.com/2008/03/9-best-practices-for-email-design/#comments</comments>
		<pubDate>Sun, 30 Mar 2008 02:44:35 +0000</pubDate>
		<dc:creator>Mr.Geek</dc:creator>
				<category><![CDATA[Webmaster]]></category>
		<category><![CDATA[email design]]></category>
		<category><![CDATA[mailist]]></category>
		<category><![CDATA[web email]]></category>

		<guid isPermaLink="false">http://albgeek.com/9-best-practices-for-email-design.html</guid>
		<description><![CDATA[Designing for an email is still quite far off from designing for a browser. In fact, email reader standards are pretty historic in the sense that (a) it requires designers to degrade their modern coding practices and (b) there really &#8230; <a href="http://albgeek.com/2008/03/9-best-practices-for-email-design/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p align="center"><a href="http://albgeek.com/wp-content/uploads/2008/03/blockedimages.jpg"><img style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px" height="150" alt="blockedimages" src="http://albgeek.com/wp-content/uploads/2008/03/blockedimages-thumb.jpg" width="150" border="0" /></a> </p>
<p>Designing for an email is still quite far off from designing for a browser. In fact, email reader standards are pretty historic in the sense that (a) it requires designers to degrade their modern coding practices and (b) there really are no true standards.</p>
<p>Fortunately, there are bodies in place that are working on standardizing the way emails are being rendered. But something tells me that we shouldn&#8217;t hold our breath (after all, we haven&#8217;t even fully standardized the experience within browsers yet). So in the mean time, here are some basic best practices to follow when designing for emails that will ensure your work displays as intended.</p>
<p>Read them all <a href="http://www.vdotmedia.com/blog/9-best-practices-for-email-design/" target="_blank">here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://albgeek.com/2008/03/9-best-practices-for-email-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

