Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Email.md – Markdown to responsive, email-safe HTML

emailmd.dev

Post reply on HN
Print view View original

91–100 of 111 posts

Re: Show HN: Email.md – Markdown to responsive, email-safe HTML

#91

Post by pembrook »

r1290 wrote: post #64
pembrook wrote: post #12

I like how you aren't hiding the fact this is MJML under the hood and don't layer complex abstractions over MJML spec like similar projects ( cough react email cough ). 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 mov…

What’s your opinion on react email?

Mostly fluff/hype. Not a value-add over just using raw MJML (which has nice VScode plugins for live previews), and in fact a long term risk to add to a codebase since react-email is just a marketing play by Resend (a startup) and will not be maintained as diligently as MJML.

Also, LLMs know MJML really well.

Re: Show HN: Email.md – Markdown to responsive, email-safe HTML

#92

Post by safehuss »

seer wrote: post #73
safehuss wrote: post #30

Anything that makes email development easier is great I guess, but have personally found MJML great for solving the issues you'd run into, and not sure I want yet another abstraction layer on top of that which makes it more limited...

They address this in the docs - it is meant to make authoring the content easier for LLMs since that is easy for them to write. 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.

If the goal is to write emails purely using AI, then it is trivial to attach the MJML documentation as context to your LLM using context7 MCP or something of the sort. It's not a very complex language and its documentation is not large at all.

That's assuming the crawlers haven't ingested it all already...

Re: Show HN: Email.md – Markdown to responsive, email-safe HTML

#93

Post by einr »

XCSme wrote: post #90
einr wrote: post #89

Earlier quoted context omitted.

Probably because it's a website and not email.

But I have to send the same sort of information (albeit shorter) via email on a regular basis. 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 email…

Yeah, I get it, I unfortunately live in the real world too. I like to keep it plain text whenever possible but it's extremely useful sometimes to have inline screenshots and stuff like that.

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.

Re: Show HN: Email.md – Markdown to responsive, email-safe HTML

#94

Post by teddyh »

deknos wrote: post #76

i never understood why the markdown mime type was not used in emailclients in webclients or desktop programs... that would eliminate most html usage and enable longer texts than 70-85 characters per line.

It’s up to the e-mail client implementors, but I would personally prefer text/enriched, RFC 1896, instead of markdown.

Re: Show HN: Email.md – Markdown to responsive, email-safe HTML

#95

Post by rcarr »

bpev wrote: post #79

I'm never seen the `::: header` or `![Logo](https://...logo.png){width="200"}` kind of syntax before. Is this custom or Frankenstein solution? Or is there some kind of md-extended pattern for defining components that has been gaining steam or smthn? Markdown tooling is always confusing, since everyone has their own standard.

https://github.com/remarkjs/remark-directive

https://talk.commonmark.org/t/generic-directives-plugins-syn...

Re: Show HN: Email.md – Markdown to responsive, email-safe HTML

#96

Post by devnotes77 »

safehuss wrote: post #30

Anything that makes email development easier is great I guess, but have personally found MJML great for solving the issues you'd run into, and not sure I want yet another abstraction layer on top of that which makes it more limited...

[dead]

Re: Show HN: Email.md – Markdown to responsive, email-safe HTML

#97

Post by runtype »

dancablam wrote: post #65
runtype wrote: post #49

Would love to use this - any plans for Cloudflare Workers support? Some of the node APIs you're using block it from working on Cloudflare right now.

Added support for cloudflare workers in 0.1.2. Thanks for the tip!

Sweet, thanks!

Re: Show HN: Email.md – Markdown to responsive, email-safe HTML

#98

Post by rbbydotdev »

bpev wrote: post #79

I'm never seen the `::: header` or `![Logo](https://...logo.png){width="200"}` kind of syntax before. Is this custom or Frankenstein solution? Or is there some kind of md-extended pattern for defining components that has been gaining steam or smthn? Markdown tooling is always confusing, since everyone has their own standard.

Admonitions are :::, allows you do to do things like this, if you have custom parser, if not, your admonitions can fail gracefully as plain text

:: gallery

![img](https://cats.com/orange-hair1.png) ![img](https://cats.com/orange-hair2.png) ![img](https://cats.com/orange-hair3.png)

::

Post reply on HN