Coding html emails is always a challenge. So oldschool in the coding practices.

Final Work

eNewsLetters are tricky things. They must survive many different challenges. First and foremost the Mail Servers that handle them. Also involved is non-user defined configurations. Some users aren’t in control of all the behaviour of their software, in controlled networks, users might be subject to various corporate implementations, ie. no images rendering in emails. So the design and implementation of the code must take these factors into consideration.

Insight Designed a few versions of the Newsletter over the years. My challenge involved making sure that the code would pass and be able to load in many different browser and email configurations. The target audience for the letters seemed to suggest that Lotus Notes (yuck!) among other industry ‘standards’ would be involved. I’ve found that fancy CSS/X-HTML code fails in many circumstances when corporate mail servers are involved.
Therefore I made the decision to use established ‘old’ templates. Unfortunately, HTML tables were used in an effort to display the layout predictably in all the targeted configurations. At least these newsletters aren’t too long so editing the code is pretty straightforward.

Another Sample

I was working for Insight Communications at the time.