#Mjml template install#

So let’s say we have to write several email templates that all share the same header, main content, and footer, and that only some text change between them: 1. Using React templating features with MJMLĮven if React is mostly known as a reactive view library, it provides all the features you would expect from a templating engine and a composition library. But as soon as you need to go a bit further, you’ll need to pair it with a templating engine, like React. So as long as you have a single email template to write, or that none of your emails needs such templating features, MJML by itself is great, and sufficient. MJML also provides a way to include external .mjml files in your templates using, which allows you to reuse some markup in several emails.īut as MJML is not a templating language, there are things it doesn’t provide, and that you might need:

#Mjml template install#

To install it from npm, without surprise: npm i mjml

It’s an awesome framework that abstract most of the pain of writing responsive HTML emails by providing a set of stylable MJML custom elements (buttons, columns, images, etc… transformed to plain HTML once built) that you can reuse to write the markup of your emails. If you ever looked up at what an email’s source code looks like, you wouldn’t even consider writing it in plain HTML (really, you can’t be that crazy)… Ī foretaste of hell (circa 2022, colorized)įortunately, MJML was created to save our souls.

Writing good looking emails is usually not the first task of your product backlog, but eventually, every product ends up needing it.