Elaboration: You can buy email templates on ThemeForest for ~$2 and they'll be prettier but it is very, very rare that they are actually as thoroughly tested as these are. Source: The guy who deals with bug reports like "It's unreadable on [insert a device that neither the designer nor the email sender owned]" way more often than he'd like to.
Fun story, which I'm telling you because it is a fun story and not because I want to scare you off using Themeforest designs: I once bought, and promptly shipped, a transactional email template. It happened to include a reproducible remote crash against at least three major versions of Outlook. (After finding this out the hard way, I reported it to Microsoft's security, which looked into it for a few months before deciding "That sucks but it doesn't look like remote code execution is actually exploitable so phew dodged a bullet there, didn't we.")
This is an amazing resource, but I don't want you to over generalize the templates at Themeforest. All the templates on that site clearly say what they have been tested in, and what clients they work in. (screenshot of the product detail sidebar: http://bluetide.pro/BU4q/1KDfhjBF). I've never ever found that info to be wrong when it says they work in the said applications. I think Themeforest does a great job with their vetting process to make sure the templates on the site are almost 100% accurate in the info.
(It may be worth reporting to Themeforest that wasn't the case on a template if you have been burned before.)
Also, if you didn't catch it in there: the [premailer] library is awesome, and helps make email templates more manageable (use CSS/LESS/SCSS styles like normal, then run your HTML email through premailer before shipping and it'll inline everything for you). I use the Python library with Django to preflight emails before sending. Works like a charm!
Also available in Ruby, Node, and PHP flavors
Several months ago, when I was using Zurb Ink to design some emails, the python premailer would choke on some of the responsive CSS. I had to switch to the ruby premailer gem to get things to work. It looks like the python premailer has since been updated, so perhaps it works now.
Yes, but not in the 1990s, which is the era HTML email finds itself stuck in.
Such a pain to build out a inlining and testing workflow for content that should be in some kind of cms.
Gotta love competition.
I also wouldn't consider open source projects as competition, there is room for everyone to work together for a common goal and they compliment each other. Some like Bootstrap and some like Foundation. Some like Rails (Ruby) and some like Laravel (PHP). Overall it's better to have more resources than less or even none. Props to all.
For those who don't know, MailChimp also has a set of email templates available. https://github.com/mailchimp/Email-Blueprints
> So what is transactional email? Coming from a MailChimp
> state of mind, you might simply think of it as "anything
> that isn’t bulk". Basically, it is email sent to an
> individual based on some action. It could be:
> * an action they took directly
> * an action they were the target of or,
> * perhaps even inaction on their part
Thanks a lot for the resource!
If anyone is interested in collaborating, I'm thinking about converting these (and the SendWithUs ones) into ActionMailer layouts and views for use in Rails apps.