It came a bit too late for my mainstay in email marketing, but I still use it for transactional emails. But a while ago, thanks to I learned about one framework that stood above all others. But they're either terrible to set up or still require you to remember a good few pitfalls in HTML email. Of course for a while now there's been solutions like Foundation for Emails, emailframe.work and many others. No really, here's a list of CSS support in email.

And funnily enough Google, the company responsible for one of the most advanced browers, is one of the worst offenders. We're talking inline styles, table layouts, transparency hacks, and so and so forth. The amount of tiny, obscure things you have to remember is incredible. Building HTML email was one of my responsibilities at my first job before I got into freelancing and I feel like in those three years I aged by at least a decade. I wish I was kidding about this, I really do.

HTML email is like the Wild West of web technologies. The amount of work that has to go into these magical creations can be absolutely mind-numbing. If you count yourself among those that have never built an HTML email before, count your blessings. So I assume that if you're reading this article, you belong to one of three categories of people: The type which has never built HTML email but wants to get into it, the type which has built HTML email before and wants to find a better way to do it and then the type who just reads everything I write for some reason. This post was originally published on my personal blog.

Mjml divider