4 ms·

No markdown, but we had success with this one: https://mjml.io/ https://mjml.io/ Try out the online examples.

by cygned 7y ago

pintxo 7y ago
Thanks, looks like a great solution.
gitgud 7y ago
Wow, that's pretty cool, what's the consistency across different clients like? Having email rendered consistently across many email clients was the main reason we stayed with Mail Chimp for so long...
- erichurkman 7y ago
  It's pretty good. A few clients are still PITA (looking at you, Outlook 2007 and Yahoo mail. You still have to do jump through hoops for accurate background images, or fancy things with borders. The actual markup MJML generates is terrifying, and can be very large payloads. A simple hero graphic, some styled body text, a few buttons, and a footer was around 60KB/message. It got gnarly for us as our MTA had a max-payload size per API 'send' call (Mandrill) so our max send rates were partially constrained by MJML's fat markup. But totally worth it to not spend _as_ much time satisfying the mail clients of the world.
  - marpstar 7y ago
    I agree with all of this. When you really start to dig in to cross-client compatibility (and you observe what MJML does to provide it) you start to get a sense that NOT using a tool like MJML is a hopeless path.
adamredwoods 7y ago
We use https://foundation.zurb.com/emails.html https://foundation.zurb.com/emails.html It is essentially rows and columns, but the support has been great across Outlook and gmail, as well as mobile support.
- justinator 7y ago
  The only problem I guess is that the last release was over three years ago, and some bugs are starting to show (saying nothing of any added features). The pace of the npm environment is moving so fast, that it's sometimes hard to even get a project up and running. Things feel a little stale. For example (from this week of my adventures with Foundation for Emails) Google Fonts almost sort of work for email, but there's just no real easy way to tell this framework to use them, or call any web font.

No markdown, but we had success with this one: https://mjml.io/ https://mjml.io/ Try out the online examples.

by cygned 7y ago

No markdown, but we had success with this one: https://mjml.io/ https://mjml.io/ Try out the online examples.

pintxo 7y ago

Thanks, looks like a great solution.

gitgud 7y ago

Wow, that's pretty cool, what's the consistency across different clients like? Having email rendered consistently across many email clients was the main reason we stayed with Mail Chimp for so long...

erichurkman 7y ago
It's pretty good. A few clients are still PITA (looking at you, Outlook 2007 and Yahoo mail. You still have to do jump through hoops for accurate background images, or fancy things with borders. The actual markup MJML generates is terrifying, and can be very large payloads. A simple hero graphic, some styled body text, a few buttons, and a footer was around 60KB/message. It got gnarly for us as our MTA had a max-payload size per API 'send' call (Mandrill) so our max send rates were partially constrained by MJML's fat markup. But totally worth it to not spend _as_ much time satisfying the mail clients of the world.
- marpstar 7y ago
  I agree with all of this. When you really start to dig in to cross-client compatibility (and you observe what MJML does to provide it) you start to get a sense that NOT using a tool like MJML is a hopeless path.

adamredwoods 7y ago

We use https://foundation.zurb.com/emails.html https://foundation.zurb.com/emails.html It is essentially rows and columns, but the support has been great across Outlook and gmail, as well as mobile support.

justinator 7y ago
The only problem I guess is that the last release was over three years ago, and some bugs are starting to show (saying nothing of any added features). The pace of the npm environment is moving so fast, that it's sometimes hard to even get a project up and running. Things feel a little stale. For example (from this week of my adventures with Foundation for Emails) Google Fonts almost sort of work for email, but there's just no real easy way to tell this framework to use them, or call any web font.