#MJML CHANGE BEETWEEN IMAGE RESPONSIVE SOFTWARE#
#MJML CHANGE BEETWEEN IMAGE RESPONSIVE CODE#

I know that until I wrote my first email template here at WeGift I’d used table elements very sparingly.

#MJML CHANGE BEETWEEN IMAGE RESPONSIVE SOFTWARE#

There is also the issue that, if you’ve only recently taken up software engineering you’re likely not very familiar with tables. We all know that one of the principles of software development is DRY (don’t repeat yourself) and HTML tables make it near impossible to stick to that principle without a huge amount of time and effort.

#MJML CHANGE BEETWEEN IMAGE RESPONSIVE CODE#

If you’re not using some sort of templating engine like Jinja where you can do then you’re going to be writing the same code over and over again.

You may also need to repeat a lot of the same code across different emails. You can of course add comments like mjml change beetween image responsive

Outlook renders using the Microsoft Word templating engine whilst Gmail and Apple use their own. You’d imagine that they’d all support the same attributes and CSS properties right? Well… no that’s far from the truth. The three most common email clients are Gmail, Outlook and Apple Mail. The fragmentation of rendering engines presents a massive challenge when attempting to make emails compatible with various email clients. Rendering engines are what take the HTML you’ve written and lay it out onto the screen for users to see. You may be thinking, why then do we use tables to construct emails when the rest of the web has moved on so much? The big issue here is that nearly every single email client uses a different rendering engine. Emails however are largely still stuck using HTML tables for their layout. Bootstrap, which allow us more control over the layout of our pages. It used to be that all webpages were built in this way but web page layout has since moved on to Flexbox, CSS Grid and other layout libraries e.g. The default way of writing email templates is with HTML tables. In the post we’ll talk about the steps I took to understand the existing problems with how we built our email templates at WeGift, the issues behind email clients and how we eventually settled on a solution to improve the process of generating email templates. However, the more we have customised our emails, the more the engineering experience has become painful, especially as the number of emails we send has grown and they’ve needed to work on a wider range of devices. For example, your latest invoice has been generated or you’ve been granted access to a new product.Īll of these emails contain critical information and we’ve attempted to present them in a design which is in keeping with our brand. At WeGift we use emails to communicate with our customers about changes on our platform.

Mjml change beetween image responsive