Zurb Ink: Responsive HTML Email Framework
51–60 of 104 posts
Re: Zurb Ink: Responsive HTML Email Framework
#52The word 'responsive' has been sprayed all over these pages. I take it I'm supposed to read that word a certain way in this context, but I don't know how. Does it mean you can click things? Something more? Something else?
Re: Zurb Ink: Responsive HTML Email Framework
#53HTML email allows an unreasonable level of deception. How does your mail client render this? http://trustworthy.host If you can't get your message across in a plain text email, you may want to reconsider whether your intent is to mislead.
> HTML email allows an unreasonable level of deception. How does your mail client render this? How does your browser render that? This isn't something unique to emails, and we didn't end up deciding that text only web pages were the way to go. That said, email clients could catch a number of simple cases like that and warn the user (yes, I realize there are ways around that). > If you can't get your message across in…
Re: Zurb Ink: Responsive HTML Email Framework
#54No no no no no no no no no no no no no no. NO HTML e-mail was and is an awful idea. My MUA doesn't need to be a browser as well. Stop the madness, please.
How else would you suggest designing an email? Plain text? Clients aren't just going to be like..."yeah, we don't want any images, or buttons, or fancy designs"... I swear all the devs on HN work in product.
Re: Zurb Ink: Responsive HTML Email Framework
#55HTML email allows an unreasonable level of deception. How does your mail client render this? http://trustworthy.host If you can't get your message across in a plain text email, you may want to reconsider whether your intent is to mislead.
You'll always have that threat. The users don't want simple text. It looks great in html most people wont even know about the risk or even understand it.
Re: Zurb Ink: Responsive HTML Email Framework
#56Lovely framework, but can someone explain why HTML email is so stuck in the past? Why can't email clients just abide by proper web standards?
Because security and privacy. There's a very good reason why your email client doesn't display images by default. Imagine every major email client allowed using HTML5/CSS3. One day somebody discovers a bug that allows you to execute random code. Now all you need to deliver a trojan to millions of people is mass-email it.
Kudos to be reasonable.
Re: Zurb Ink: Responsive HTML Email Framework
#57Earlier quoted context omitted.
How else would you suggest designing an email? Plain text? Clients aren't just going to be like..."yeah, we don't want any images, or buttons, or fancy designs"... I swear all the devs on HN work in product.
Why do emails need to be designed in the first place? Honest question.
The better question would be, why does design matter?
This list could be huge but here are a few common reasons:
- To simplify information.
- To make it more digestible.
- To be engaging. To invoke emotion.
If you blast an average email receiver with a poorly designed wall of text, at best, they might read part of it and drop out half way through. Most of them will archive or delete it without even opening it and another portion will probably report it as spam.
I won't sit here and discuss the complexities of why design matters but here are a few links:
- http://www.fastcodesign.com/3019604/design-50/design-in-30-s...
- http://articles.latimes.com/2013/sep/30/business/la-fi-mo-wo...
Re: Zurb Ink: Responsive HTML Email Framework
#58The word 'responsive' has been sprayed all over these pages. I take it I'm supposed to read that word a certain way in this context, but I don't know how. Does it mean you can click things? Something more? Something else?
'Responsive' simply means that a layout adjusts itself to the size of the device/screen. See: http://en.wikipedia.org/wiki/Responsive_web_design
Re: Zurb Ink: Responsive HTML Email Framework
#59There should be an option to email the docs page with examples to one self. In order to preview it in your own mail inbox(s).
Re: Zurb Ink: Responsive HTML Email Framework
#60Lovely framework, but can someone explain why HTML email is so stuck in the past? Why can't email clients just abide by proper web standards?