Remaking the Sass News Newsletter

By Mike Street

With the weekly golden nectar of Sass News winging its way into my inbox every week, I decided to take on the challenge of giving the newsletter a facelift (if you're not subscribed and you like Sass - you should do it)

Many people would run away at the thought of designing and making a HTML newsletter, but I strangely enjoy it!

Mailchimp have a fantastic resource of email blueprints to get you started. You can pick and chose from a whole myriad of templates - with cross-client compatibility. The other sites i've often referenced and used are Zurb's Ink framework and Antwort

With mobiles and emails taking off, responsive mailouts are paramount. No-one wants to be zooming in and out on a mobile just to read the text!

I picked the basic single column responsive layout and started modifying colours and fonts, taking hints from the current mailout. I felt the current mailout was missing emphasis on the different sections and an image to draw the user in.

To make sure the mailout worked with the length and type of content that Stu would be sending out, I knocked up a couple of the past ones - making sure links worked and acted as expected in all the browsers.

To save time, I used <style> blocks at the top of the page while prototyping and getting the mailout looking sweet. Those that build mailouts know that Outlook (and other clients) don't play well with style blocks - preferring inline styles. Rather than going through each element and replacing the class with style tags, I used mailchimp's amazing css inline tool - it saved an absolute ton of time!

Once built with initial content, I ran a few inbox tests. Putsmail is a great service for creating and sending HTML newsletters for free - It enables you to send to up to 10 accounts at a time and it's a great, easy way of checking all sorts of email clients and devices. Always measure twice cut once, just becuase the change you made will "probably work", there is nothing worse than sending a big mailout and realising you missed an </a>. Its also a good idea to look at the statistics of previous mailouts if you can, there is no point sweating over a missing border in Outlook 2003 if only 1 person uses it.

If you've ever had to do regular (or even irregular) mailout creations, you quickly realise that copying and pasting <td> is tedious, boring and sometimes dangerous. Missing that vital </tr> can be the difference between your mailout getting 1000s of clicks and it going into spam. It also takes a long time, working out where one story starts and another ends.

To speed up development of the Sass newsletter, I made it dynamic - running off a json file so the mailout does the heavy lifting of working out where to loop stories. I have used php to convert the json into an object

I started off by dividing the mailout up into stories and sections - and working out where each one is: (this is not the actual code - just example!)

You can see - even for a basic example thats already a few lines of code!

Once I had separated out the newsletter into sections, I started to build the json up:

{
"title" : "Welcome to Issue #17",
"intro_text" : "This issue features fun, frolics and even more articles from Hugo!",
"content" : [
{
"image" : "http://www.mikestreety.co.uk/image1.png",
"title" : "Speak at Sassconf",
"text" : "Got a great idea for a talk or workshop? The closing date for submissions to this years Sassconf has been extended to May 30th. "
}, {
"image" : "http://www.mikestreety.co.uk/image2.png",
"title" : "Speak at Sassconf",
"text" : "Got a great idea for a talk or workshop? The closing date for submissions to this years Sassconf has been extended to May 30th. "
}
]
}

We have the structure and the content - we just need to tie the two together. Saving the json in a separate file enables us to pull it in and decode using php.

<?php $email = json_decode(file_get_contents('content.json')); ?>

The variable $email is now an object with all the data from the file. To get the title and intro text, output the title and intro_text properties on the $email object:

Any bugs with the news story html only needs to be adjusted once, plus if you update the article title, it will update the <img> alt tag too. From there, upadting the newsletter each week is as simple as updating the JSON and copying the compiled HTML.