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...
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 you need to author a lot of emails with LLM you should be rethinking your business strategy tbh
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...
[dead]