HTML
There’s text and then there’s text
If you want to send someone an email with some text in it there are quite a few different ways you can do it. The main differences are the ways the text is packaged up in MIME entities to be sent.
Read More10 things every mailer must do
A bit of a refresh of a post from 2011: Six best practices for every mailer. I still think best practices are primarily technical and that how senders present themselves to recipients is more about messaging and branding than best practices. These 6 best practices from 2011 are no longer best, these days, they’re the absolute minimum practices for senders.
If you can’t manage to do these, then find someone who can.
Email design resources
One of the more frequent questions I get that I can’t answer is how to design a good email. Design is just not my strong point and outside actually getting the HTML right, what an email looks like doesn’t have a whole lot to do with delivery. It was pointed out to me today that the nice people over at Mailchimp have a resource page for designing emails. It’s a good mix of theory and explanation and some code examples.
Very useful if you’re trying to create pretty HTML emails from scratch.
Mail that looks good on desktop and mobile
Over the weekend I noticed a new CSS framework aimed at email rather than web development, “Antwort“.
This isn’t the first or only framework for email content, but this one looks simple and robust, and it allows for content that doesn’t just adapt for different sized displays but looks good on all of them. The idea behind it is to divide your content into columns, magazine style, then display the columns side-by-side on desktop clients and top to bottom on mobile clients. That opens up much more interesting designs than the more common single fluid column approach.
It looks nice, it supports pretty much every interesting email client, but it also comes with some directions based on real world experience.
Six best practices for every mailer
People get into all sorts of details when talking about best practices. But so much of email depends on the type of email and the target market and the goals of the sender. It’s difficult to come up with universal best practices.
I’ve said in the past that I think that best practices are primarily technical. I don’t believe there is a best frequency or a best time to send mail or a best image to text ratio.
My top 6 best practices every marketer should be doing (and too few are).
Character encoding
This morning, someone asked an interesting question.
Last time I worked with the actual HTML design of emails (a long time ago), <head> was not really needed. Is this still true for the most part? Any reason why you still want to include <head> + meta, title tags in emails nowadays?
Read More
Creating effective links
CampaignMonitor blogged today about an email they sent out that triggered the Thunderbird “this might be a scam” filter.
Read MoreHTML in email
Steve and I were talking this afternoon about HTML in email. He wanted to know what headers I looked for in the HTML portion of an email. A good question, as I’ve seen everything from a full doctype declaration through to just <body> tags.. All of them seem to render OK in various mail clients so I don’t spend too much time worrying about the specific HTML header elements. I do look for invalid tags and comments, but I check those whether they are in the header or the body.
Those of you that design HTML emails, what are your experiences with headers? Are there specific HTML headers that you always include? Do you skip the header portion of the HTML document and just use body tags? How do you test? What do you think is important?