Email Templates
The email template system turns MJML source into responsive, branded HTML emails. Templates are authored once, rendered on demand for any number of recipients, and support reusable building blocks, multilingual copy, and design-time previews.
What it gives you
- Author in MJML. A high-level markup language designed for responsive email.
No more wrestling with
<table>layouts. - Reusable fragments. Define a button, a header, a footer once and embed it in any template. Edit it in one place, every template picks up the change.
- Data-driven content. Each template binds to a typed model. Fields like
{{ Order.OrderNumber }}are replaced with real values at send time. - Multilingual. Translation keys plus a locale produce the right copy in the right language without forking the template.
- Recipient-aware. Dates and times render in each recipient's own timezone, language, and clock preference — automatically, with nothing timezone-specific in the template.
- Live previews. Send sample data, get back the final HTML before a single email is dispatched.
- Versioning and lifecycle. Templates carry an explicit version and a Draft / Published status so changes can be staged safely.
When to use it
Use the email template system whenever your application sends customer-facing mail that varies by data, language, or recipient — order confirmations, event notifications, password resets, invoices, and so on.
Next steps
| Topic | What it covers |
|---|---|
| Templates | The core unit: what a template is and what it carries. |
| Fragments | Reusable MJML components and shared styles. |
| Variables & data | Binding a template to a typed model. |
| Localization | Multi-language copy via translation keys. |
| Filters | Transforming values inline: translation, dates, ranges. |
| Rendering & previews | From MJML to final HTML. |
| Versioning & lifecycle | Draft, Published, version bumps. |