Designers

Here are some best practices for making HTML Newsletters

File Naming

It’s important to keep file naming consistent with all of lour client’s newsletters. Naming all your feature images as img#.jpg will allow for you to not need to change that bit of code every month. the HTML file should be named as follows: The file should be named using the following convention: ClientName_MonthYear.html.  By extension, it’s important that we all name them the same, not only across clients, but across designers for the same reason.

File Pathing

Following the same filing structure across the board also allows fro us to eliminate a step in the coding process. It will also allow for us to eventually memorize client folder paths and eliminate the need for us to look up the file path every time we need to get a link to a specific file or flipbook.

File Sizes

When designing for web, it’s important that we keep the file size as low as possible. There are several factors that contribute to file size: file type, file PPI, and file dimension. JPGs, PNGs, and GIFs are all good file types to use for web. The ideal file PPI for web is 72 PPI. You can use 150PPI, but you must then make sure that your dimensions are twice that of the allotted space. With our HTML newsletters, it’s important that we keep dimension consistent, depending on which template you are using.

Project Managers

iFrames

This is a solution for the client that wants to have the flipbook display on one of their webpages. It’s still hosted through us, but it displays on their page. This means that we can pull it from being posted.

File Names

The URL we give to clients should be almost all the same from month to month. The only thing that should change is the month on the end of the URL.

Sending Fileshtml_icon

This is what the file that you send to the client should look like. The icon should be as shown on the right, but the layout of the email can vary. The file should be named using the following convention: ClientName_MonthYear.html

 

↓