This is cool!
I looked for this in the past. This is the main reason we bothered with mailchimp/hubspot -- simply the ability for nontechnical marketing people to put together nice emails, and the trust that we won't need an engineer to troubleshoot email formatting on their behalf. I remember trying some OSS tools at the time (8 years ago?) and there were some templates we used but then when we wanted to modify them, the broken-ness of email html/css standards made it really hard to test.
I know the standards and practice around this are a moving target, though, so I hope you can find a model to sustain and expand this, without charging for delivery/contact list numbers like MailChimp or other incumbents.
I got you a gold star ;) Excited to use this, as I've been frustrated by vendor lock-in for this exact use case.
This is really nice, thanks for building. I will use that heavily :)
does it store our data persistently on your server/system
Hi looks nice. I am in the process of building a email management system for a client with a small coaching base, and decided to go with Maily to integrate with the React and resend stack.
I hadn't heard of beefree or unlayer before this post. What would you say are the reasons we would want to use Templatical over our current integration or Beefree/unlayer?
Thanks.
[dead]
[flagged]
[dead]
Picking MJML as the output format instead of raw HTML is the move. That's the layer where the cross-client pain has already been solved by people more patient than any of us.
Two questions:
1. How extensible is the block system? Can consumers define their own block types with custom MJML output, or are you limited to the built-ins?
2. Any plans for a headless render path (JSON → MJML → HTML on a server) for transactional emails generated from templates at send time?
Either way, bookmarking. Been waiting for someone to do this without the SaaS tax.