Live data from Hacker News

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

emailmd.dev

81–90 of 111 posts

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

#81
post #63

Any "HTML emails" get filtered straight into the spam folder here. I think I'm not part of the target audience here.

How do you deal with things like "we sent you a one-time code to confirm your login"? Most of those are HTML-formatted today

I still can check the SPAM folder, if needed.

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.) :)

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

#82

Feels more like a content layer for LLMs than a replacement for MJML. In my experience models tend to break HTML layouts pretty easily, while Markdown degrades more gracefully.

It uses MJML under the hood.

https://mjml.io/

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

#83
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.

Yep both are widely used. I forget which markdowns extensions they originated from. The Pandoc website probably has the details.

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

#84

Markdown is the secret winner of the AI early years.

I'm not so sure. It's definitely the de facto standard, but I suspect minimal HTML is better. Just enough tags to add structure and meaning (H1-H6, p, a, em, section for structure including nesting, maybe more). LLMs were trained on a lot of HTML, they're good at processing it. HTML requires more tokens than markdown but I believe it's worth it. I'll find out in a few weeks as I experiment with both.

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

#86
post #8

I wish people just sent plain text.

What about images, links? Formatted text like bold or underline? 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.

> What about images, links? Formatted text like bold or underline?

Easy. Don't.

That's the great bit. You don't have to.

https://useplaintext.email/

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

#87
post #86
post #8

Earlier quoted context omitted.

What about images, links? Formatted text like bold or underline? 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.

> What about images, links? Formatted text like bold or underline? Easy. Don't. That's the great bit. You don't have to. https://useplaintext.email/

Why isn't this website plain text then?

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

#88
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.

Yep both are widely used. I forget which markdowns extensions they originated from. The Pandoc website probably has the details.

Aye, I've seen these both in kramdown and quarto.

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

#89
post #87
post #86

Earlier quoted context omitted.

> What about images, links? Formatted text like bold or underline? Easy. Don't. That's the great bit. You don't have to. https://useplaintext.email/

Why isn't this website plain text then?

Probably because it's a website and not email.

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

#90
post #89
post #87

Earlier quoted context omitted.

Why isn't this website plain text then?

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 emails.

Post reply on HN