Live data from Hacker News

Show HN: I built an open-source email builder, alternative to Beefree/Unlayer

play.templatical.com

51–60 of 63 posts

Re: Show HN: I built an open-source email builder, alternative to Beefree/Unlayer

#51

YES! This is so needed. Also very happy to see it's Vue + TipTap. Great choices.

Thanks :)

I know each framework has its pros/cons, opinionated in a certain way. Vue is my favorite.

TipTap was the easy half. It's basically the go-to option when a good WYSIWYG editor is needed.

Re: Show HN: I built an open-source email builder, alternative to Beefree/Unlayer

#53
post #43

As someone who built a similar open source project (grapesjs), this looks really good Even with LLMs, generating raw HTML emails that render correctly across major email clients is still surprisingly hard, so great choice going with MJML.

Holy shit, it's you! Thank you, that genuinely means a lot coming from you! GrapesJS is the forever OG that proved this whole space could be an embeddable SDK rather than a paywalled SaaS. It also standardized the palette/canvas/inspector layout that every serious visual builder now ships by default — including Templatical. I took direct inspiration from a few other patterns too: the block-as-first-class-citizen mode…

Honestly, I didn’t invent anything particularly new, but I deeply appreciate your words. Thank you.

Really happy to see people building great things in this space and pushing it forward. Wishing you and Templatical the best!

Re: Show HN: I built an open-source email builder, alternative to Beefree/Unlayer

#56
This is awesome! I've always had trouble designing my emails in Figma first and then coding the HTML. For some reason, I just can't wrap my head around it any other way (I might not be the best at coding, tbh). Thanks for putting this together—I'm definitely going to give it a shot!

Re: Show HN: I built an open-source email builder, alternative to Beefree/Unlayer

#59

Earlier quoted context omitted.

Thanks — this is exactly the audience I built it for. The cross-client rendering thing is why Templatical outputs MJML instead of raw HTML. MJML was built to abstract all the table-based, Outlook-2007-quirks, Gmail-strips-style nonsense — you write semantic blocks, MJML compiles to table HTML that works across every major email client. So when your marketing person moves a block or changes a button color, it doesn't…

Even when using mjml you must do render tests of your templates using litmus or a similar service. Mjml is WAY better than hand rolling templates but there are foot guns to be found and the docs won’t mention most of them https://github.com/mjmlio/mjml/issues/2927#issuecomment-2539... .

Totally agree on edge case quirks of MJML - or more like weird behaviors in Outlook. With so many email services and clients around, nothing can provide 100% bulletproof solution but I think MJML is as close as it gets to works-for-majority. I‘m sure MJML maintainers also aim for this.

Also, yes! Microsoft should kill Outlook with fire! :)

Re: Show HN: I built an open-source email builder, alternative to Beefree/Unlayer

#60

This is awesome! I've always had trouble designing my emails in Figma first and then coding the HTML. For some reason, I just can't wrap my head around it any other way (I might not be the best at coding, tbh). Thanks for putting this together—I'm definitely going to give it a shot!

Believe me, writing HTML for email that works for most clients is notoriously hard, no amount of code experience can help with that :)

This was exactly the reason I went with MJML. Consumer should focus on designing the email, Templatical takes care of converting the design to MJML and rest with MJML is already battle-proven.

Post reply on HN