<?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>Ex Machina: Jack Graham&#039;s Blog &#187; HTML CSS email</title>
	<atom:link href="http://jackgraham.net/exmachina/tag/html-css-email/feed/" rel="self" type="application/rss+xml" />
	<link>http://jackgraham.net/exmachina</link>
	<description>The Worklife of a Software Business Analyst, Unlicensed Futurist, and Tech Wonk-of-all-Trades</description>
	<lastBuildDate>Thu, 08 Mar 2012 19:54:17 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Coding HTML &amp; CSS for bulk e-mails</title>
		<link>http://jackgraham.net/exmachina/2009/09/10/coding-html-css-for-bulk-e-mails/</link>
		<comments>http://jackgraham.net/exmachina/2009/09/10/coding-html-css-for-bulk-e-mails/#comments</comments>
		<pubDate>Thu, 10 Sep 2009 16:50:48 +0000</pubDate>
		<dc:creator>Jack Graham</dc:creator>
				<category><![CDATA[e-mail marketing]]></category>
		<category><![CDATA[HTML CSS email]]></category>

		<guid isPermaLink="false">http://jackgraham.net/exmachina/?p=72</guid>
		<description><![CDATA[I&#8217;m presently reviewing resumes and work samples for a new interactive producer position at our company. In the process, I&#8217;ve been struck by how few people know the basics of coding mass marketing e-mails. At the core of it, there are only two rules: Use tables for layout, not CSS. Embed all CSS styles in [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright size-thumbnail wp-image-77" title="e" src="http://jackgraham.net/exmachina/wp-content/uploads/2009/09/e-150x150.jpg" alt="e" width="150" height="150" />I&#8217;m presently reviewing resumes and work samples for a new interactive producer position at our company. In the process, I&#8217;ve been struck by how few people know the basics of coding mass marketing e-mails. At the core of it, there are only two rules:</p>
<ol>
<li><strong>Use tables for layout, not CSS.</strong></li>
<li><strong>Embed all CSS styles in block level elements.</strong></li>
</ol>
<p>And that&#8217;s pretty much it. Point 2 deserves a little bit of elaboration, though.</p>
<p>The reason for embedding styles is that some ESPs (Gmail, I&#8217;m looking at you) ignore style sheets in the &lt;head&gt;  section of the document. They also ignore &lt;span&gt; tags, and inheritance can be a bit wonky. The safest course of action is to use style attributes in block level elements such as &lt;div&gt;, &lt;p&gt;, &lt;h#&gt;, &lt;a&gt;, and the like.</p>
<p>This makes Dreamweaver a huge pain to use for e-mails, because it does the exact opposite of this. One of my co-workers who&#8217;s in marketing hired a freelancer to do some e-mails for her, and she found that they weren&#8217;t displaying very well. The freelancer in question had requested a copy of Dreamweaver within minutes of sitting down to work. I&#8217;d advise those making hiring decisions on someone to create e-mails to be skeptical of potential hires who indicate that they rely heavily on Dreamweaver. E-mail is still a hand coder&#8217;s game.</p>
<p>Some coders use the &lt;font&gt; tag, as well, but I disagree with this on the grounds that &lt;font&gt; is deprecated HTML and should not be used. &lt;font&gt; does allow for the possibility of creating styling inside of a block level element without creating a line break (which happens in some ESPs if you use &lt;div&gt;), but I don&#8217;t think it&#8217;s a worthy trade-off. I&#8217;m advocating deprecated coding techniques (e.g., table layouts), but I won&#8217;t advocate deprecated code.</p>
<p>This brings me to my final point. Just because e-mails needs to be coded in a way that flies in the face of what would be considered best practices in building a web page doesn&#8217;t mean it&#8217;s acceptable to produce lousy code overall. While following these guidelines, one should still strive to produce code that&#8217;s readable and validates for whatever flavor of HTML was used.</p>
<p><em>Photo: <a href="http://www.sxc.hu/profile/CraigPJ" target="_blank">Craig Jewell</a> via stock.cchng</em></p>
]]></content:encoded>
			<wfw:commentRss>http://jackgraham.net/exmachina/2009/09/10/coding-html-css-for-bulk-e-mails/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

