3 ms·
Yeah, it made me think about a funny thing that happened to me a month ago: Last month I created the template for an HTML email on behalf of my brother. Based
by jessep 18y ago
Yeah, it made me think about a funny thing that happened to me a month ago:
Last month I created the template for an HTML email on behalf of my brother. Based on the advice of MailChimp (http://www.mailchimp.com/resources/how_to_code_html_emails.phtml http://www.mailchimp.com/resources/how_to_code_html_emails.p...), I used tables for layout. It worked on my first try. I could NOT believe how easy it was.
Due to the dirty feeling I get from using tables, I didn't let myself consider using tables more broadly for layouts. But now ... I feel like an alchoholic saying, "maybe just one little drink."
- swombat 18y agoWhen I put together the new email template for our site ( http://woobius-dev.posterous.com/enhancing-the-look-of-the-emai http://woobius-dev.posterous.com/enhancing-the-look-of-the-e... ) I went straight for tables. And, unsurprisingly, it worked great in all email clients right off the bat. I don't feel dirty from using tables now. I use floating divs whenever it makes sense, but if it takes too long to screw around with the divs, or if it feels like it will take too long, I switch to tables in a heartbeat. Otoh, there's something to be said for the various grid css layouts out there, like Blueprint and the like. They might be contrived, but they work pretty well on a wide variety of browsers. Where reasonable, I still favour using something like Blueprint rather than tables. Not sure why, though...