Erlang is a programming language used to build massively scalable soft real-time systems with requirements on high availability. Some of its uses are in telecom, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance.
OTP is set of Erlang libraries and design principles providing middle-ware to develop these systems. It includes its own distributed database, applications to interface towards other languages, debugging and release handling tools.
We prefer to receive proposed updates via email on theerlang-patches mailing list or through a pull request.
Pull requests will be handled once everyday and there will be essential testing before we will take a decision on the outcome of the request. If the essential testings fails, the pull request will be closed and you will have to fix the problem and submit another pull request when this is done.
We merge all proposed updates to the pu (*proposed updates*) branch, typically within one working day.
At least once a day, the contents of the pu branch will be built on several platforms (Linux, Solaris, Mac OS X, Windows, and so on) and automatic test suites will be run. We will email you if any problems are found.
If a proposed change builds and passes the tests, it will be reviewed by one or more members of the Erlang/OTP team at Ericsson. The reviewer may suggest improvements that are needed before the change can be accepted and merged.
Copyright Ericsson AB 2010-2012. All Rights Reserved.
The contents of this file are subject to the Erlang Public License, Version 1.1, (the "License"); you may not use this file except in compliance with the License. You should have received a copy of the Erlang Public License along with this software. If not, it can be retrieved online at http://www.erlang.org/.
Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License.
The best way to understand any process is to carry it out yourself, from the ground up. Today, we're going to do just that with email design, by building an HTML email template from scratch.
Kick Things Off
To begin with, it's worth mentioning where I pulled some of the resources from.
With that sorted, we can commence building the rest of the structure.
Creating the Body and Main Table
First, we’ll add an overall structure for our email, starting with a <body> tag. We'll set the margin and padding on the body tag to zero to avoid any unexpected space.
We'll also add a table with a width of 100%. This acts as a true body tag for our email, because styling of the body tag isn’t fully supported. If you wanted to add a background color to the ‘body’ of your email, you’d need to apply it to this big table instead.
Set your cellpadding and cellspacing to zero to avoid any unexpected space in the table.
Note: We’re going to leave border="1" on all of our tables, so that we can see the skeleton of our layout as we go. We’ll remove them at the end with a simple Find & Replace.
If an attribute exists in HTML, use that instead of CSS
Now place a centered table of 600 pixels wide inside the container table. 600 pixels is a safe maximum width for your emails to display comfortably within most desktop and webmail clients on most screen resolutions.
Set this width using HTML instead of CSS, by using the width attribute. The golden rule in HTML email development is: if an attribute exists in HTML, use that instead of CSS.
We’ll replace our little ‘Hello!’ greeting with this table:
We've also added an inline style property that sets the border-collapse property to collapse. If we don’t do this, newer versions of Outlook will add a small space between our table and our border.
Creating the Structure and Header
In our design we can see that the email is divided into three logical sections, so we'll create a row for each.
Let’s duplicate the single row we already made so that we have three in total. I’ve changed the text inside them so that we can easily identify each row.
Now we’ll color them according to the design. As bgcolor is a valid HTML attribute, we'll use that to set the background color instead of CSS. Always remember to use the full six characters of a hex code, as three character shorthand won’t always work.
Ok, next up we are going to focus on Row 1. We want to adjust the padding on the cell and then insert our image.
Using Padding
When using padding in email, you must always specify every single value (top, right, bottom and left) otherwise you can get unpredictable results. I find that you can still use the shorthand, i.e. padding: 10px 10px 8px 5px;, but if you are having trouble you may wish to write it out longform, i.e. padding-top: 10px; padding-right: 10px; padding-bottom: 8px; padding-left: 5px;.
If you are having even greater troubles with padding (for example, if your send platform is stripping out your CSS), don’t use it at all. Simply use empty cells to create space. There is no need to use spacer GIFs, just make sure you add style="line-height: 0; font-size: 0;" to the cell, place an inside and give it an explicit height or width. Here is an example:
Also note that it’s safe to use padding on TD tags but not on P tags or DIVs. They behave a lot more unpredictably.
So, we’ll use some inline CSS to add padding to the cell. Then we’ll insert our image, adding alt text and adding style="display:block;" which is a common fix that stops some email clients adding gaps underneath your images. We’ll center the image by adding align="center" to our td tag. We’ll also add an alt tag which is important for when our email is initially loaded which, in most cases, will be with images off.
Note: If the contents of your header are really important to your message, don’t use an image-only header. Remember, images are blocked by default for most clients, so if there is an aspect of your email that is crucial, never include it as an image. In this example, however, my header is pretty superfluous.
First off, we’ll add some padding to the middle cell so that the table inside has some space around it, as per our design.
Now we’ll add a table with three rows for our main content — one for the headline, one for the introductory text, and one for the row with two columns. We'll set the width of this table to 100% rather than using a pixel value because this will help us further down the track if we want to make our email responsive. If you always have pixel widths on everything, you can end up with a lot of values to override with media queries. If your nested table widths are based on percentages, then when you adjust the width of the parent element, everything will adapt accordingly.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. In tempus adipiscing felis, sit amet blandit ipsum volutpat sed. Morbi porttitor, eget accumsan dictum, nisi libero ultricies ipsum, in posuere mauris neque at erat.
</td>
</tr>
<tr>
<td>
Row 3
</td>
</tr>
</table>
Now we are going to add our two columns of content to Row 3. Because we want a ‘margin’ in between these two cells, but margin isn’t supported, we’ll create a three-column table with an empty cell between the two outer columns.
As much as I like to stick to percentages, when you have content that is a specific size, it can be tricky to convert it to a percentage (in this example, the columns would be 48.1% which could become confusing). For this reason, since our two images are 260px wide, we’ll create columns that are also 260px wide, with a 20px margin cell in the middle. (This will total 540px, which is the 600px width of our table minus the padding of 30px on either side.) Be sure to zero your font-size and line-height and add a a non-breaking space character in the margin cell.
We'll also set the valign to "top" for both cells so that they will vertically align to the top, even if one column has more text than the other. The default vertical alignment is "middle".
Now let’s add our images and content to those columns. As we need multiple rows, we'll nest yet another table because we can’t use any colspan or rowspan tags. We’ll also add some padding in between the image and copy in each column.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. In tempus adipiscing felis, sit amet blandit ipsum volutpat sed. Morbi porttitor, eget accumsan dictum, nisi libero ultricies ipsum, in posuere mauris neque at erat.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. In tempus adipiscing felis, sit amet blandit ipsum volutpat sed. Morbi porttitor, eget accumsan dictum, nisi libero ultricies ipsum, in posuere mauris neque at erat.
</td>
</tr>
</table>
</td>
</tr>
</table>
Here we have set the width of the images using HTML at 100% of the column width. This, again, is so that if we make this email responsive, we only have to use media queries to change the width of the parent element. We'll have to override the height in pixels because using style="height: auto" now won’t work in everything (cough cough, Outlook). So we’ll set it using pixels. This means we'd have to set height: auto!important on those images using media queries to override the pixel value, but we could do that with a single class. As we set the width as a percentage, we won’t need to override that. The fewer things to override, the better.
We’ll create another little table for our social media icons. We’ll set its parent cell to align="right". Make sure you set border="0" on these image links (to avoid a blue link border) and don’t forget display:block.
Now we’ll add our text and add a width to our cells, just to be safe, even though there is a lot of whitespace between them. We'll set this cell to 75% and the other to 25%.
1
2
3
4
<tdwidth="75%">
® Someone, somewhere 2013<br/>
Unsubscribe to this newsletter instantly
</td>
And there we have it! Our layout is complete.
Validation
Let's run this through the W3C Validator to make sure nothing is bad or broken. If you’ve followed along exactly, it will say that it has passed.
Next we’re going to run a test through Litmus to make sure the structure of our email works great. Here’s a summary of my test:
Next we need to style the footer text, and we’ll also tidy up our unsubscribe link. We'll style our unsubscribe text link using both CSS and the HTML <font> tag. This doubling up is the best way to ensure that your links never show up in the default blue.
<ahref="#"style="color: #ffffff;"><fontcolor="#ffffff">Unsubscribe</font></a> to this newsletter instantly
</td>
And there we have it! Everything is in. Time to turn off the borders and see it looking beautiful. Go through and replace every occurance of border="1" with border="0".
At this point, it’s looking a little sad floating in white space, so let’s go up to our first 600px wide table and add:
1
style="border: 1px solid #cccccc;"
Now it doesn’t look like it’s floating anymore. As a final touch, I’m going to add 30px of padding to the bottom of the very first cell, to prevent our email from stopping abruptly at the bottom in some webmail clients (like Apple Mail), and 10px of padding at the top, so that our blue header has a little bit of breathing room.
Promin is a simple jQuery plugin that lets you break your forms into smaller chunks so they consume less space. It’s also a unique way of presenting forms.
Daux.io is a simple to use documentation generator that uses Markdown files to create custom documentation in a developer-friendly way. It’s responsive, automatically creates a homepage/landing page, auto generates your navigation, and comes with 4 built-in themes.
