:: gallery
  
::
that would eliminate most html usage and enable longer texts than 70-85 characters per line.
But most SPAMs are HTML, so you'll have a good default last-stage in-client filtering in place in case some SPAM actually makes it through the other setup on the server (greylisting, DNS based filtering lists, policy-based filtering, etc.) :)
In my experience models tend to break HTML layouts pretty easily, while Markdown degrades more gracefully.
When I see a news article, I want to be able to click a button on my Mac or iPhone to send the text of the article in the body of the email. Bonus points for rehosting the images from the article. And using a similar font both without carrying over any of the original external dependencies.
Normally it’s good to support the journalist but I cannot in good conscience send a link to elderly folks when this is so much safer.
For the next three intriguing articles you see on arbitrary sites, does the select all trick produce an aesthetically pleasing email? Do external dependencies get carried over? Do you spend any time manually removing cruft? Does the formatting leave anything to be desired?
When I do this all manually I can make it look great, and now that we’ve seen we can train computers to make stuff look great, it’s going to be a point of frustration for me until I have the one-click beautiful-article-email button.
I also prefer plain text, but in most of my emails I talk about technical stuff, or I send transactional emails that require actions, in which case showing buttons is a much better user experience than plain text.
You could have a larger text instead of a button, but changing font size is also HTML and not plain-text anymore.
I don't think so. I certainly didn't have to resort to HTML to make that link readable and clickable.
Those templates should account for all types of people and accessibility levels (including things like ADHD, where you need a big red button to click, otherwise you get overwhelmed by a block of text).
Easy. Don't.
That's the great bit. You don't have to.
A lot of alerts, reporting, quotes, code snippets, short documentation or step by step instructions, etc.
I don't just send emails to say "Hey, let's meet at 5". You know the memes with "this could have been an email", it usually is this case.
Just to be clear, most of those rich emails are the automatic/transactional emails.
I didn't mean to be sarcastic but it's just that to me, philosophically, email is a plaintext technology that had HTML bolted on to it kicking and screaming, and it's always been kind of crap. People like me hate things that are fundamentally ugly and crap even if they are useful. The web was designed for HTML from the start.
The devs maintaining MJML deserve so much credit for dealing with Gmail/Outlook's monopoly bullshit and 2007 html.
Nice idea for those who manage content in markdown. I've moved away from putting emails in my codebase, but seems great for founders moving fast.
Also, LLMs know MJML really well.
Pretty sure I've said it before, but it would be a nice middle ground between text and all the complexity HTML+CSS brings in (if you want to compete with other HTML clients).
I'm in this "group" and see an immediate usefulness of this over what I'm doing now.
It still uses MJML for the actual templates, but it is a translation layer between markdown and the template itself.
If you need to author a lot of emails with LLM this does seem like it would be a great fit.
That's assuming the crawlers haven't ingested it all already...