mjml file and you can see how that can be a little jarring. Compare that to an MJML project which is exactly one. But it's still huge and has over 2,000 files. Now this folder is for development only, once you're ready to test and deploy you have a single HTML file. But there were a few things that I didn't really enjoy First it was the project file itself: when you create a new project (which is to say, one email) you do so on the command line and you end up creating a +~200MB folder. It's very robust, has support for partials, and using SASS in email development was a dream come true (email developers, as it turns out, dream nerdy dreams). But the truth is I wasn't exactly blown away.įoundation 2 is an excellent framework.
This is the same method you use when writing MJML).
#MJML TABLE CODE#
Now I would write straight Inky code rather than using "Inky HTML" (the difference is that originally you'd write HTML with some Inky thrown in but now you write in Inky with HTML thrown in.
As good as MJML 1.0 was I knew that Foundation 2 would dominate. I was exactly as excited as I had been all along. Now all that said, about a month or two after I started using MJML then Foundation for Emails 2 (using v2. Then when you want to get a little more serious you can throw in your own HTML/CSS at will and MJML will spit out a beautiful email (providing the design itself is beautiful 😜) that's pretty much ready to go into testing and deployment. I really enjoy the experience of typing up straight MJML code especially for prototypes. If you do have HTML experience and, more specifically HTML email experience of course, then it'd take you about 5 minutes to put together a great if not basic email. The MJML syntax is EXTREMELY simple and if you've got absolutely no HTML experience you can start coding up really good emails in I would say maybe an hour or two (once you get used to dealing with the command line). Intrigued by the post I quickly visited the website and downloaded through NPM and started combing through the online docs. I actually came across it one day in a Litmus newsletter that mentioned exciting Community posts. MJML started as a project internally to MailJet and from my understanding grew pretty rapidly to become a real value-adding project that they decided to release into the wild. And when Zurb announced that they were cooking up V2 I waited impatiently for months until the day it was released.but by then I had found MJML.
#MJML TABLE FULL#
Getting used to writing "Inky" HTML was a tiny bit of a challenge but once I got the hang of it I was coding at full speed. I used it in several production projects and shaved hours off my dev time and greatly increased my ability to target emails cross-platform - it was wonderful. It's easy to use and has tons of utility built right in. But I personally enjoy MJML because it's mobile-first and forward thinking, the syntax is nicer, and the support community is astounding.
0 kommentar(er)
