The Moms Can Code community is so helpful. Not only do we have an excellent supportive community of very different individuals, we also have all kinds of training - brought to us by brave members. Lucky, lucky me for being a part of this group.
Folks who follow me on twitter know I have been working frankly, more than I care to admit on improving the quality of emails coming from the gifts-done site when people do things or don’t do things. All of those emails are still in development, but I’m getting close.
This morning, I was able to watch a training (I watched the recording because I couldn’t make it to the live version) on coding an email newsletter. Erica walked us through getting started with MailerLite and setting up images using Canva and even showed how to start with a template and whittle it down to what you actually want to show. Watching her do it live (well, recorded) was excellent. If you are a Moms Can Code member, go watch it right now.
After watching the training video, I set out to make my own newslettter. Here is where I landed. I made a fake newsletter that would show my most recent coding posts from this blog. Basically, I tried to imagine what would I want to get in my email from a coding blog, and I made that.
My email newsletter on an iPad pro (per Chrome dev tools)
You can see an image at the top and the bottom that I built using Canva, starting with a template for Email header. The links to my blog include a related image (either one that I included in the post or otherwise) and the title. Then, I have three social network logos that link to my profiles on those networks so that subscribers would be able to easily reach out with questions or to see what I’m up to.
Before whipping this up, I looked at several templates, and I finally set the code up myself based on the transactional emails that I have been building and the guidance from Erica. The base of those transactional emails is from templates from MailGun - and their discussions about email have been invaluable to me.
Here is the code that I used - I think this could be simplified a little to be shorter, but not much. When you look at this code, there are two big things to note:
Everything in an HTML email needs to be a table. This means that you need to think through how things should be aligned. Also, I have heard that some email clients do not do well with multiple columns, so you should try really hard to keep email to one column where possible.
All styles need to be inline in HTML email This means that you need to code everything directly by hand or use a preprocessor to inline your css styles. While I’ve seen several inlining tools, this one from inliner has got to be the easiest if you are not doing it by hand. Since I was copying and pasting from a template I had already built upon from another template, I just built more inline styles. However, if you are trying to match your website styles and don’t want to type them all, try out an inliner.
The difficult thing about email is that there are so many applications and devices used to access email. Some of them add or process your HTML before delivering it to the user. That means that your email, while it looks pretty in your browser, may look quite terrible in another platform. I have not tried it yet, but I hear good things about Litmus for testing your email in multiple - I think they have 90 right now - email clients. I did send the email to myself, so I can vouch that it looks pretty in iPhone Mail and in GMail on Chrome.
The only thing I regret here is that I had not been collecting subscribers to this blog already, so I would have a natural audience for this pretty newsletter.
I am going to add a subscription form soon. In the meantime…If you are interested in getting updates from me, let me know via twitter.