<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Geoff Kimball on Medium]]></title>
        <description><![CDATA[Stories by Geoff Kimball on Medium]]></description>
        <link>https://medium.com/@geoffkimball?source=rss-bbda55c52ce4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*s3uUc_YshYWKyS_QXPCHnA.jpeg</url>
            <title>Stories by Geoff Kimball on Medium</title>
            <link>https://medium.com/@geoffkimball?source=rss-bbda55c52ce4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:59:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@geoffkimball/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Dear Ueno: How do I make great-looking emails?]]></title>
            <link>https://medium.com/ueno/dear-ueno-how-do-i-make-great-looking-emails-bffeef7bffeb?source=rss-bbda55c52ce4------2</link>
            <guid isPermaLink="false">https://medium.com/p/bffeef7bffeb</guid>
            <category><![CDATA[dearueno]]></category>
            <category><![CDATA[email-development]]></category>
            <category><![CDATA[email-marketing]]></category>
            <dc:creator><![CDATA[Geoff Kimball]]></dc:creator>
            <pubDate>Tue, 24 Jul 2018 13:09:42 GMT</pubDate>
            <atom:updated>2018-08-16T12:40:17.636Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Dear Ueno is an advice column for people who for some weird reason think we know what we’re doing. Read </em><a href="https://medium.com/ueno/dear-ueno-b6946471b26a"><em>more about all this</em></a><em>, or check out our </em><a href="https://loremipsum.ueno.co/dear-ueno/"><em>old advice</em></a><em>.</em></p><p><strong><em>Malte in Germany asks:</em></strong></p><blockquote><em>“What is your approach to make beautiful emails? Is there any user-friendly way to combine HTML with content that works on most devices well?”</em></blockquote><p><strong><em>Geoff Kimball, developer at Ueno SF, answers while wearing a funny hat:</em></strong></p><p>Hello, Malte!</p><p>I’m so glad you want to get into email design. Most of your skills in design and development will transfer, but you’ll have to pick up some new tricks. Some <em>highly-specific-to-email-development </em>tricks.</p><p>When you design an email, the approach is pretty similar to how you’d design a website: think about your audience and what your goals are, and create a design that meets those ends. <a href="https://www.campaignmonitor.com/blog/email-marketing/2018/04/7-stats-that-will-make-you-rethink-mobile-email/">More than 50% of emails are opened on phones</a>, so make sure your design is mobile-friendly, and get to the point, because you’re working with limited screen space.</p><p>Also, make sure your email mostly makes sense without images—some mail clients block images within emails by default. Use alt text on images so they can be “read” instead of viewed.</p><p>Lastly, be careful with your visual design, because you’re much more limited in what you can do within the confines of an HTML email. No complex animation and no interactivity besides links. There are also certain types of CSS like background images that don’t always work, so you’ll either have to avoid them in your design, or get used to coding clever hacks to get around the limitations.</p><h3>And now for the weird stuff</h3><p>The world of email development is vast, like an ocean, and also deep, like an ocean. It’s also scary, like an ocean, but instead of sharks, you have Microsoft Outlook. So let’s dive in! Trust me, it’s <em>fine</em>.</p><p>When we build websites, we make sure that they’re functional and look about the same in every web browser. Chrome, Firefox, Safari, and so on. Okay, Internet Explorer is a little weird, but you can figure it out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/1*kpSInLkGaGIdsrc4mgcNqA.png" /><figcaption>This is what our newsletter looks like in Outlook 2010. Thankfully, nobody on our mailing list uses Outlook 2010.</figcaption></figure><p>Email isn’t so simple. You’re still doing cross-client compatibility checks—you look at your email on iOS Mail, Gmail, Yahoo!, Outlook, and so on. But many old email clients just don’t handle HTML and CSS the way you’d expect. For example, <a href="https://litmus.com/blog/a-guide-to-rendering-differences-in-microsoft-outlook-clients">Microsoft Outlook 2007, 2010, and 2013 use Microsoft Word to render emails</a>. Yes, they use <em>a word processor</em> instead of an actual web browser.</p><p>It keeps getting weirder. Many email clients randomly don’t support various CSS properties (like float), CSS selectors (like .class), or even entire HTML tags. Some email readers rip out anything you put in a &lt;head&gt; tag—there goes all your CSS!</p><p>But the show must go on, so new techniques were invented to accommodate the wealth of bizarre behaviors on display in email clients. Instead of writing CSS in a &lt;style&gt; tag, we plant all of the CSS on each HTML element directly, known as inlining:</p><pre>&lt;table style=&quot;width: 100%; float: left; background-color: pink&quot;&gt;&lt;/table&gt;</pre><p>To build grid-based layouts, we use HTML tables instead of floats or flexbox. You know, <em>tables</em>—those things we stopped using for layout like a decade ago? It turns out tables are one of the few things that work consistently across mail clients. In 2013, the open source project Ink (now called <a href="https://foundation.zurb.com/emails.html">Foundation for Emails</a>) was released, which took the Bootstrap/Foundation-style 12-column grid and converted it to use tables, allowing you to easily build grid-based layouts in an email. Since then, more tools have sprung up to streamline email development.</p><h3>Malte, are you still there?</h3><p>Don’t worry, it’s not as bad as it looks! We’ve established that building emails is weird. Thankfully, there are a ton of resources out there to make it easier.</p><p>First off, all that stuff about tables or whatever? Forget it. These days, there are great open source tools out there that let you code emails in a simpler form of HTML, that is <em>automagically </em>converted into the complex, battle-tested HTML you need. They can also help you with all that weird CSS business, or help you bundle up your email for final delivery.</p><p><a href="https://foundation.zurb.com/emails.html">Foundation for Emails</a> and <a href="https://mjml.io/">MJML</a> are two of these great tools. They both feature a custom HTML syntax that hides all the scary bits of working with HTML emails. For example, here’s how you create a button with <a href="https://foundation.zurb.com/emails.html">Foundation for Emails</a>:</p><pre>&lt;button href=&quot;ueno.co&quot;&gt;Ueno&lt;/button&gt;</pre><p>And here’s the final HTML it creates:</p><pre>&lt;table class=&quot;button&quot;&gt;<br>  &lt;tr&gt;<br>    &lt;td&gt;<br>      &lt;table&gt;<br>        &lt;tr&gt;<br>          &lt;td&gt;&lt;a href=&quot;ueno.co&quot;&gt;Ueno&lt;/a&gt;&lt;/td&gt;<br>        &lt;/tr&gt;<br>      &lt;/table&gt;<br>    &lt;/td&gt;<br>  &lt;/tr&gt;<br>&lt;/table&gt;</pre><p>Now that’s a time-saver! You’ll still have to be careful how you write your code, however. For that, I have a few go-to resources:</p><ul><li><a href="https://www.campaignmonitor.com/css/">Campaign Monitor’s Ultimate Guide to CSS</a>: a support table that shows you what CSS you can and can’t use in various email clients.</li><li>The <a href="https://litmus.com/blog/">Litmus blog</a> and <a href="https://www.emailonacid.com/blog/">Email on Acid blog</a>: two great blogs on all things email: design, copywriting, development, and more.</li></ul><p>You’ll also need to test your emails, to make sure they work in all of these weird email clients. Thankfully, you don’t need a PC with a copy of Outlook 2003—there are email testing services that let you upload an email, and then generate screenshots of the email in whatever clients you want. Two of those services are <a href="https://litmus.com/">Litmus</a> and <a href="https://www.emailonacid.com/">Email on Acid</a>. Email marketing services like <a href="https://mailchimp.com/">MailChimp</a> also have email testers, so you can test and send your emails all in one place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sH47oEg10QH-hwWalkkqXg.png" /><figcaption>Tools like Litmus make it easy to test your email on dozens of mail clients at once.</figcaption></figure><h3>A case study: Ueno’s newsletter</h3><p>Using all of the tools above, we lovingly, painstakingly craft the Ueno newsletter once a fortnight for our beautiful audience. <a href="https://github.com/ueno-llc/newsletter">The code is open source!</a></p><p>It’s a small custom build process that pulls in a bunch of existing email tools, combining them into one handy workflow.</p><ul><li>The emails are written using Foundation for Emails’s grid system and custom HTML syntax.</li><li>The HTML also uses Handlebars, so we can split code into repeatable chunks and add some logic to the code.</li><li>The CSS is written in Sass, so we can split code into separate files, and store common design elements in variables.</li><li>The email can be previewed in a BrowerSync server, which automatically reloads the page when a file is updated.</li><li>A single build command inlines the CSS, compresses the email, and bundles the HTML and placeholder images into a .zip file we can upload to MailChimp.</li></ul><p>We test emails with Litmus and deliver them with MailChimp. Our template also takes advantage of <a href="https://mailchimp.com/help/create-editable-content-areas-with-mailchimps-template-language/">MailChimp’s editable fields feature</a>, so our content folks can write a newsletter every two weeks without needing to consult a developer.</p><h3>Brave the treacherous waters</h3><p>What have we learned today? Microsoft Outlook is weird, tables are somehow good, and developing emails requires a lot of patience, but thankfully there’s years and years of knowledge out there to help you, and great open source tools to streamline things.</p><p>So if email development is scary like an ocean, think of all these resources as those cages you can dive in to look at sharks. Now get out there and make some beautiful emails!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ich4L3yhYaa_GExrFz4Z8Q.png" /></figure><p><em>Geoff Kimball is a developer at Ueno who likes people, places, and things. Want to work with him? Check out </em><a href="https://www.ueno.co/careers"><em>available positions at Ueno</em></a><em>.</em></p><p><em>To submit questions to Dear Ueno, email </em><a href="/service/mailto:hi@ueno.co"><em>hi@ueno.co</em></a><em> with the subject line “Dear Ueno” or </em><a href="https://twitter.com/uenodotco"><em>tweet at us</em></a><em> with the hashtag #DearUeno. Include your (optionally fake) name, location, and profession. Ok, thanks.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bffeef7bffeb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ueno/dear-ueno-how-do-i-make-great-looking-emails-bffeef7bffeb">Dear Ueno: How do I make great-looking emails?</a> was originally published in <a href="https://medium.com/ueno">Ueno.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dear Ueno: How should a designer communicate animations and interactions to a development team?]]></title>
            <link>https://medium.com/ueno/dear-ueno-how-should-a-designer-communicate-animations-and-interactions-to-a-development-team-405b006e1b14?source=rss-bbda55c52ce4------2</link>
            <guid isPermaLink="false">https://medium.com/p/405b006e1b14</guid>
            <category><![CDATA[animation]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[dearueno]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Geoff Kimball]]></dc:creator>
            <pubDate>Mon, 19 Mar 2018 18:59:56 GMT</pubDate>
            <atom:updated>2018-08-16T12:54:39.477Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Dear Ueno is an advice column for people who for some weird reason think we know what we’re doing. Read </em><a href="https://medium.com/ueno/dear-ueno-b6946471b26a"><em>more about all this</em></a><em>, or check out our </em><a href="https://loremipsum.ueno.co/dear-ueno/"><em>old advice</em></a><em>.</em></p><p><strong><em>Daniel in San Jose asks:</em></strong></p><blockquote>“What is the best way for a designer to communicate animations and interactions to a development team? I see a lot of beautifully animated websites out there but can’t figure out how people bridge that communication gap between design and development in terms of animation.”</blockquote><p><strong><em>Geoff Kimball, developer at Ueno SF, replies in the approachable and relatable manner he’s known for:</em></strong></p><p>Hey Daniel. How is San Jose?</p><p>I left town for the big city of San Francisco about a year ago, but as much as people like to call San Jose “boring,” or “lame,” or “Man Jose,” I’d move back in a heartbeat. Have you been to 7 Stars Bar &amp; Grill? It’s my favorite bar in San Jose, with Jack’s Bar &amp; Lounge in Japantown a close second. And if you’re ever at the sandwich place Togo’s on 1st and Heading, tell them I’m sorry I left after three years without saying anything. I have trouble with goodbyes.</p><p>But I digress. Let’s talk about animation.</p><p>On the list of “things about front-end that are complicated,” animation is up there for me with writing a Webpack config correctly on the first try. Here below are some high-level ideas about team communication that might help you smooth out your handoff process in the future.</p><h3>A few words about designers and developers</h3><p>Sometimes people talk as if we’re in an adversarial relationship. And in some work environments, we are segmented in such a way that things do become adversarial: designers make thing, developers code thing, and ne’er the two shall meet.</p><p>But this isn’t how we make our best work. We make our best work as a team, communicating with each other and understanding each others’ needs. Shipping a digital product isn’t an assembly line: it’s a big, complicated, beautiful mess, and you’ll get through it best with constant communication between everyone on the team, regardless of their role.</p><h3>Time is marching forward without stopping, and our planet is circling one of billions of stars in a vast, uncaring cosmos</h3><p>Animation takes time, and can be a big, potentially hidden cost. If you know your team is going to invest in animation for a site, it’s great for the developers to know that early on. I’ll often build things slightly differently if I know something is going to animate, so having that up-front knowledge gives me time to do some prep work. And if you show me stuff while you’re working on it, that’s a huge help.</p><p>As a team, decide on an appropriate scope for animation, the same way you would for page count. This ensures everyone is on the same page and happy about the final result. And if things slip? Don’t fret! It’s a normal part of the product development cycle. Just make sure everyone agrees on how to move forward.</p><p>And be explicit about as much as you can. Motion prototyping is a huge help to a developer, and there’s no shortage of tools for it these days: After Effects, Framer, Principle, and more. (Bonus advice: Give your developer the original source file, so she can comb through it and recreate the animation as accurately as possible.)</p><h3>Down with those silos</h3><p>The “handoff” is not one singular event. Communication between designers and developers should be happening continually. It ensures everyone is on the same page, and cuts down on the number of surprises in the whole process. Remember, designers and developers are not separate teams — you’re on one team, working towards a common goal.</p><p>At Ueno, designers try involve developers before the final handoff so they can help with the project timeline. Likewise, we encourage designers to be involved in the development process here and there — it makes everything go smoother.</p><p>So ask your project manager to budget some extra time for you to follow up and communicate with developers when things come up. After all, the project isn’t done until the thing has been built and shipped.</p><h3>Developers: Be fearless</h3><p>Now this last bit is for developers, and it’s a <em>secret</em>. So if you’re not a developer, stop reading.</p><p>.</p><p>.</p><p>.</p><p>.</p><p>.</p><p>.</p><p>Hello, developers. Python C# cache invalidation version control SSL iPod sandwich Progressive Web App React. Haha, get it?</p><p>So your team has the budget, and you’ve got the motion study. But you still gotta build the thing. You know that feeling where you’re looking at a mockup and you think, “I’ve never done this before,” or “I’m not sure how I’m going to make this work”? Tackle those challenges head-on. Essential to the advice I’ve given in this answer is trust and understanding. Earn that by being a go-getter.</p><p>This is definitely one of those “easier said than done” things, but it’s essential to growing in any creative or technical field. And it only becomes easier with experience. When you encounter a problem you don’t know how to solve, get excited — it means you get to learn something new.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*etLPhwoohSx2sOpB_jaLdg.png" /></figure><p><em>Geoff Kimball is a developer at Ueno who once saw a guy on the train carrying a huge lizard in his jacket. He’s currently seeing how long he can go </em><a href="https://twitter.com/geoffkimball"><em>without tweeting</em></a><em>. Want to work with him? Check out </em><a href="https://www.ueno.co/careers"><em>available positions at Ueno</em></a><em>.</em></p><p><em>To submit questions to Dear Ueno, email </em><a href="/service/mailto:hi@ueno.co"><em>hi@ueno.co</em></a><em> with the subject line “Dear Ueno” or </em><a href="https://twitter.com/uenodotco"><em>tweet at us</em></a><em> with the hashtag #DearUeno. Include your (optionally fake) name, location, and profession. Ok, thanks.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F9ff108%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2F9ff108%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/0ab8a34c9014698c61343e5b02314cdd/href">https://medium.com/media/0ab8a34c9014698c61343e5b02314cdd/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=405b006e1b14" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ueno/dear-ueno-how-should-a-designer-communicate-animations-and-interactions-to-a-development-team-405b006e1b14">Dear Ueno: How should a designer communicate animations and interactions to a development team?</a> was originally published in <a href="https://medium.com/ueno">Ueno.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>