Ideas, insights and inspirations.

Here at Elliance, we practice what we preach — sending responsive emails just as we encourage our clients to do. Our upcoming newsletter will be our first. (If you don’t currently receive the newsletter and want to check out the result, contact us with the ‘Sign Up for Newsletter’ box checked.) The importance of making websites responsive is well known — it’s been the hot topic in web design for some time now. But there isn’t as much being published about the importance of responsiveness in emails. Think about the emails you read today. What did you read it on? On your desktop email client, like Outlook or Thunderbird? On your browser using GMail, Hotmail, or corporate webmail? On your phone or tablet using a built in client? In the few hours I’ve been awake this morning, I can tell you I’ve read an email using each of these methods. I’m not an edge case when it comes to my … Continue reading

Posted in:

In typically self-effacing manner, Ethan Marcotte deflected the gobs of praise and gratitude being offered to him today, on the two-year-anniversary of his seminal A List Apart article in which he first described what’s come to be known as Responsive Web Design. I think this deserves one tiny footnote, and that’s that Ethan didn’t simply write an article. That’s misleadingly humble. Ethan got tenaciously interested in solving a particular problem related to how a proliferating variety of devices and browsers displayed websites. Yes, the author community caught the fever, spreading and advancing the technique, but before Ethan’s article delivered Responsive Design to ALA readers, he noticed something, got intensely curious about it, and put in a lot of dedicated effort to satisfy his curiosity. That’s the part I’m thankful for, and it’s why congratulations are most certainly in order.

Posted in:

Once upon a time, a project (the making of, let’s call it, “The Product”) would go like this: Having finished discovery, the project lead, an information architect, and a content strategist would articulate the site’s purpose, structure, content strategy, and page requirements. This would take the form of a package of deliverables including spreadsheets, site maps, and wireframes – henceforth called “The Package”. Next, one or more visual designers – now invited into the project for the first time – would review the The Package, ask questions about The Package, reinvent parts of The Package, discard parts of The Package, and produce a proposed design based on the modified Package. Naturally, the designers’ renovations called for the re-entry of the information architect and content strategist, despite the fact that our process frequently made such re-entries inconvenient if not unfeasible. The project lead, information architect, content strategist, visual designer, and project manager would now enter into the cavernous stomach of a … Continue reading

Posted in: , , , , , ,