smangela: E-mail Design & Development Guidelines pt 1 & 2

part 1: June 18, 2009

Unified standards, specifications, and best practices have made it possible for web designers to increase the accessibility and usability of the sites they’re designing while ensuring that the sites look the same no matter what browser is used. Unfortunately, no such standards presently exist for email design which is why emails face a number of rendering issues that differ among ISPs...read on
-
part 2: June 23, 2009
No CSS...read on
- - -
Part 2 only has three lines and is only one sentence. I am also not sure if it even correct seeing as you can use CSS in your email but it must be 'in-line' and not in a style tag or a linked external style sheet using classes and id.
eg:
<style>
 td {font-family:arial;font-size:12px;}
 .style1 {font-size:14px;}
<style>
<td><span class="style1">hello</span>world</td>

is wrong, it should be:
<td style="font-family:arial;font-size:12px;"><span style="font-family:arial;">hello</span>world</td>

This is rather inconvenient for web 2.0 people as you have to add the style attribute to every single tag rather than just referencing it from the top directly or through it's class but that is the only way that works. Also not all stylings are rendered, eg: bakground images are not popular and often ignored, margin, border, float - also not consistently rendered in all inboxes, check the email standards project for the full details - Outlook 2007, using Word to render is the worst and even after a giant campaign from the ESP blog to FixOutlook, Microsoft do not seem to be in a rush to fix word's html rendering or writing.

-