1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
|
Title: HTML Email Generation
HTML Email is apparently the killer feature for everyone who uses email.
The first, second, and third question I get asked when I tell people
about Lamson is, "Does it do HTML email?!" Yes it does, and hopefully
in a very nice clean way that'll make blasting out all that great
marketing material your users *love* easier than ever.
bq. The fourth question is whether Lamson handles bounces. "Yes it does.":/docs/bounce_detection.html
h2. A Few Tips About HTML Email
First, you *must* educate your marketing people that your user's "Inbox is not a TV.":http://myinboxisnota.tv/
I actually run "myinboxisnota.tv":http://myinboxisnota.tv/ just to make a point that people who
do marketing have the wrong idea of people's Inbox experience. It's your job as the hacker to
educate them and make sure that they know users actually mostly hate HTML email, and that sending
them an HTML email is nothing like sending them a commercial on TV.
The next tip is a technical one related to how you have to craft your HTML. Lamson's
"lamson.html":http://lamsonproject.org/docs/api/lamson.html-module.html API actually
helps you get this right, but you need to understand it in order to appreciate what
it does for you.
The rule when crafting your HTML is that you need to code for browsers of circa 1995
with no ability to use @style@ tags or @script@ tags. Most of the various HTML viewing
clients strip or disable these making them useless. This means you have to put all
CSS stylings inline into your HTML, and you have to rely on "taboo" tags like @center@
and @table@ for your layout.
h2. The Structure Of HtmlMail
The "lamson.html.HtmlMail":http://lamsonproject.org/docs/api/lamson.html.HtmlMail-class.html class
is responsible for generating all your HTML emails. How it works is you give construct one
with an "outer template" and a "CleverCSS":http://sandbox.pocoo.org/clevercss/ template as your
CSS stylesheet. This builds a generator that you then hand an internal version of your email
to generate the content for each user.
This combination of outer template+CleverCSS and inner markdown content means that you can
use the markdown content also as your text version, since markdown actually looks half-decent
as a text format.
Here's a simple example that shows this process in action:
<pre class="code prettyprint">
generator = html.HtmlMail("style.css", "html_test.html", {})
resp = generator.respond({}, "content.markdown",
From="zedshaw@zedshaw.com",
To="zedshaw@zedshaw.com",
Subject="Test of an HTML mail.",
Body="content.markdown")
</pre>
First, we make a generator passing in the CleverCSS stylesheet @style.css@,
and the Jinja2 HTML template @html_test.html@. Then we call @HtmlMail.respond@
to craft a "lamson.mail.MailResponse":http://lamsonproject.org/docs/api/lamson.mail.MailResponse-class.html
that you can then hand to "lamson.server.Relay":http://lamsonproject.org/docs/api/lamson.server.Relay-class.html
for delivery.
There's also a couple of tricks in the above email. First, notice that the
second parameter is "content.markdown", but that we also pass in the Body="content.markdown".
This little convenience tells the HtmlMail object that you want to reuse the
raw @content.markdown@ file as the text/plain version of the email.
Finally, once you make the generator you can keep calling @respond@ to spit out
each message you want.
h2. The HTML CSS Conversion
None of the above code shows you what is the nicest part of this API. The lamson.html
API will actually take plain HTML and your CleverCSS and insert the @style@ attributes
into it for you. Let's look at an example from the unit test (that's disgusting).
First we have the CleverCSS template:
<pre class="code prettyprint">
body:
margin: 10
padding: 20
background: green - 30
color: blue
h1:
font-size: 3em
h2:
font-size: 2em
color: yellow
h3:
font-size: 1em
p:
padding: 0.3em
background: red
h2:
color: yellow
#bright:
background: black
color: white
.dull:
background: gray
color: black
</pre>
Then we have the raw original HTML:
<pre class="code prettyprint">
<html>
<head>
<title>{{ title }}</title>
</head>
<body style="background: magenta">
<h1 class="bright">{{ title }}</h1>
{{ content }}
<h3 id="dull">All done.</h3>
</body>
</html>
</pre>
Notice this is a template too, and that {{ content }} is your @content.markdown@ file
from the earlier discussion.
Now when you run this (including the content.markdown not shown here), Lamson produces
this:
<pre class="code prettyprint">
<html>
<head>
<title></title>
</head>
<body style="background: magenta; margin: 10; padding: 20; background: #006200; color: blue">
<h1 class="bright" style="font-size: 3em; background: black; color: white"></h1>
<h1 style="font-size: 3em">Hello</h1>
<p style="padding: 0.3em; background: red">I would <em>love</em> for you to tell me what is going on here joe. NOW!</p>
<h2 style="font-size: 2em; color: yellow; color: yellow">Alright</h2>
<p style="padding: 0.3em; background: red">This is the best I can come up with.</p>
<p style="padding: 0.3em; background: red">Zed</p>
<h3 id="dull" style="font-size: 1em; background: gray; color: black">All done.</h3>
</body>
</html>
</pre>
Which, if you code for a Web 2.0 company is probably making your eyes bleed Dijon mustard, but it
works. Lamson has walked your HTML and inserted all the style tags it could, including
keeping any you already had there.
h2. Conclusion
With Lamson HTML email API you should be able to blast out all the wonderful HTML you need
to prop up your sales needs for years to come. It does the best it can to make it easy
to still work in a modern web methodology, but produce the nasty HTML that has the highest
chance of working in most email clients.
|
