Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://www.zeldman.com/rss/

  1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
  2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  3. xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  4. xmlns:dc="http://purl.org/dc/elements/1.1/"
  5. xmlns:atom="http://www.w3.org/2005/Atom"
  6. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  7. xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
  8. >
  9.  
  10. <channel>
  11. <title>Zeldman on Web &amp; Interaction Design</title>
  12. <atom:link href="http://www.zeldman.com/feed/" rel="self" type="application/rss+xml" />
  13. <link>http://www.zeldman.com</link>
  14. <description>Web design news and insights since 1995</description>
  15. <lastBuildDate>Tue, 21 Nov 2017 15:15:45 +0000</lastBuildDate>
  16. <language>en-US</language>
  17. <sy:updatePeriod>hourly</sy:updatePeriod>
  18. <sy:updateFrequency>1</sy:updateFrequency>
  19.  
  20. <image>
  21. <url>https://i0.wp.com/www.zeldman.com/wp-content/default-54a3966bv1_site_icon.png?fit=32%2C32</url>
  22. <title>Zeldman on Web &amp; Interaction Design</title>
  23. <link>http://www.zeldman.com</link>
  24. <width>32</width>
  25. <height>32</height>
  26. </image>
  27. <site xmlns="com-wordpress:feed-additions:1">1178115</site> <item>
  28. <title>Faux Grid Tracks by Eric Meyer</title>
  29. <link>http://www.zeldman.com/2017/11/21/faux-grid-tracks-eric-meyer/</link>
  30. <pubDate>Tue, 21 Nov 2017 15:15:45 +0000</pubDate>
  31. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  32. <category><![CDATA[A List Apart]]></category>
  33.  
  34. <guid isPermaLink="false">http://www.zeldman.com/?p=14618</guid>
  35. <description><![CDATA[<p>JOIN An Event Apart’s Eric Meyer on a journey through the inner workings of CSS Grid as he tests various techniques to build a tic-tac-toe board filled with content. Hearkening back to the early days of CSS and A List Apart, these playful hacks rekindle a spirit of experimentation. Faux Grid Tracks by Eric Meyer [&#8230;]</p>
  36. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/11/21/faux-grid-tracks-eric-meyer/">Faux Grid Tracks by Eric Meyer</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  37. ]]></description>
  38. <content:encoded><![CDATA[<p><img class="alignnone size-full wp-image-14619" src="https://i0.wp.com/www.zeldman.com/wp-content/faux-grid-illo_960_454_81.jpg?resize=640%2C303" alt="" srcset="https://i0.wp.com/www.zeldman.com/wp-content/faux-grid-illo_960_454_81.jpg?w=960 960w, https://i0.wp.com/www.zeldman.com/wp-content/faux-grid-illo_960_454_81.jpg?resize=100%2C47 100w, https://i0.wp.com/www.zeldman.com/wp-content/faux-grid-illo_960_454_81.jpg?resize=768%2C363 768w" sizes="(max-width: 640px) 100vw, 640px" data-recalc-dims="1" /></p>
  39. <p>JOIN An Event Apart’s Eric Meyer on a journey through the inner workings of CSS Grid as he tests various techniques to build a tic-tac-toe board filled with content. Hearkening back to the early days of CSS and A List Apart, these playful hacks rekindle a spirit of experimentation.</p>
  40. <p><a href="https://alistapart.com/article/faux-grid-tracks" target="_blank" rel="noopener nofollow" data-ft="{&quot;tn&quot;:&quot;-U&quot;}" data-lynx-mode="async" data-lynx-uri="https://l.facebook.com/l.php?u=https%3A%2F%2Falistapart.com%2Farticle%2Ffaux-grid-tracks&amp;h=ATMe-T3MOR4d6TWBYp6uWyWxWyWuQnestVUkgK82FgPe2zl1n5f9gmxio3T0iY3N342sMz_VncPVdXtQmHUlLC8ZlfAu21x_rZWU9MvyxowGQVso-ObGf5tyZVfJLTNv9q9qTSluNfeQJpMUweZb9cCajAGRou3gmFZBRXtU1cDQUA5-dDytaGcPEJWnr9o74WpdmBPqOR6GIK3Tf03vyeW2jqk693iSaVCvoVNzMAMFG2iouIuELwpY8bWfijR-p_LCzp6tLEcaejWOcKTTxT5PWA52Z2Fj-zGtJHoHczY">Faux Grid Tracks by Eric Meyer</a></p>
  41. <p>&nbsp;</p>
  42. <p><em>Illustration by Dougal MacPherson</em></p>
  43. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/11/21/faux-grid-tracks-eric-meyer/">Faux Grid Tracks by Eric Meyer</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  44. ]]></content:encoded>
  45. <post-id xmlns="com-wordpress:feed-additions:1">14618</post-id> </item>
  46. <item>
  47. <title>A Dao of Responsive Liquid</title>
  48. <link>http://www.zeldman.com/2017/11/19/dao-responsive-liquid/</link>
  49. <pubDate>Sun, 19 Nov 2017 18:18:53 +0000</pubDate>
  50. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  51. <category><![CDATA[Web Design History]]></category>
  52. <category><![CDATA[Web Standards]]></category>
  53. <category><![CDATA[Websites]]></category>
  54.  
  55. <guid isPermaLink="false">http://www.zeldman.com/?p=14596</guid>
  56. <description><![CDATA[<p>A liquid page will resize to fit whatever size browser window (within reason) that the user has available. … the real goal in building a website is to provide the user with a seamless interface to information. The site should not intrude on the user’s thought processes, but should gently guide them to their desired destination. [&#8230;]</p>
  57. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/11/19/dao-responsive-liquid/">A Dao of Responsive Liquid</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  58. ]]></description>
  59. <content:encoded><![CDATA[<p><img class="softinset" src="https://i0.wp.com/www.zeldman.com/wp-content/1_Gy9ixjdJTWI39SncGQMZAQ.png?w=640" alt="" data-recalc-dims="1" /></p>
  60. <blockquote><p>A liquid page will resize to fit whatever size browser window (within reason) that the user has available. … the real goal in building a website is to provide the user with a seamless interface to information. The site should not intrude on the user’s thought processes, but should gently guide them to their desired destination. If a site doesn’t look right because it doesn’t fit the user’s browser window, then the design has become intrusive to the user. — Glenn Davis, <a class="markup--anchor markup--pullquote-anchor" href="http://www.zeldman.com/15/davisf.html" target="_blank" rel="noopener nofollow" data-href="http://www.zeldman.com/15/davisf.html"><strong class="markup--strong markup--pullquote-strong">quoted in 15 Minutes, sometime in 1997</strong></a>.</p></blockquote>
  61. <p id="ea11" class="graf graf--p graf-after--pullquote">TWO DECADES before <a class="markup--anchor markup--p-anchor" href="https://alistapart.com/article/responsive-web-design" target="_blank" rel="noopener nofollow" data-href="https://alistapart.com/article/responsive-web-design"><strong class="markup--strong markup--p-strong">Responsive Web Design</strong></a>, we dipped our toes in <a class="markup--anchor markup--p-anchor" href="http://www.zeldman.com/15/davisf.html" target="_blank" rel="noopener nofollow" data-href="http://www.zeldman.com/15/davisf.html"><strong class="markup--strong markup--p-strong">Liquid Layout</strong></a> — a similar but necessarily less refined concept. Glenn Davis of Project Cool fame coined the phrase in 1995 or 1996. (<a class="markup--anchor markup--p-anchor" href="https://web.archive.org/web/20040701041831/http://www.digital-web.com/articles/liquid_web_design/" target="_blank" rel="noopener nofollow" data-href="https://web.archive.org/web/20040701041831/http://www.digital-web.com/articles/liquid_web_design/"><strong class="markup--strong markup--p-strong">Glenn also came up with</strong></a>“Ice” to describe fixed-width layouts, and “Jello” for layouts that combined some fixed with some flexible elements.)</p>
  62. <p id="9310" class="graf graf--p graf-after--p">Liquid Layout was mainly what <a href="http://www.johnfallsopp.com/"><strong>John Allsopp</strong></a> had in mind when he wrote <a class="markup--anchor markup--p-anchor" href="https://alistapart.com/article/dao" target="_blank" rel="nofollow noopener" data-href="https://alistapart.com/article/dao"><strong class="markup--strong markup--p-strong">A Dao of Web Design</strong></a> for <em class="markup--em markup--p-em">A List Apart</em> (quite possibly the most influential article we ever published). The most famous paragraph in that famous article explains…</p>
  63. <blockquote><p>The control which designers know in the print medium, and often desire in the web medium, is simply a function of the limitation of the printed page. We should embrace the fact that the web doesn’t have the same constraints, and design for this flexibility. But first, we must “accept the ebb and flow of things.”</p></blockquote>
  64. <h4>Everything new is old</h4>
  65. <p id="23cb" class="graf graf--p graf-after--h3">Modern designers look back at Allsopp’s article and think John must have been a time traveler who had seen the future of responsive design and mobile devices. In fact, though, John was simply a highly skilled (and extremely articulate) mainstream developer. As such, he was familiar with Liquid Design and frequently used it in his work, along with other ideas mentioned in “Dao,” such as not forcing users to see a particular type size or typeface. To a good developer in those days, what mattered was making something that worked for everyone. (That should <em class="markup--em markup--p-em">still</em> be what good developers care most about, right?)</p>
  66. <p id="0459" class="graf graf--p graf-after--p">Liquid design was part of a “works for everyone” approach to web design, but it had limitations. For one thing, breakpoints hadn’t been invented. CSS layout was in its infancy, used by almost no one, except in experimental work. The ability to separate content and behavior from presentation was nonexistent, unless you limited “presentation” to setting type in a single column, letting the user override the type setting, and letting the column reshape itself to fit any viewport.</p>
  67. <p id="3813" class="graf graf--p graf-after--p">With so few controls available, Liquid design tended to become unusable in certain settings, and was almost always ugly.</p>
  68. <h4>Liquid design was Responsive design’s rough draft</h4>
  69. <p>Liquid design was immediately popular with developers when they were given permission to just make stuff — i.e. when they weren’t constrained by overly rigid Photoshop layouts. Designers almost never used Liquid design because the layouts moved so quickly into ugliness and unusability — too wide to read, or too narrow, or with overlapping columns in early CSS layouts. Designers also disdained Liquid layouts because most of us see our job as imposing brilliant order on ugly chaos, and fixed proportions always seemed to be part of that order.</p>
  70. <p><a href="https://i0.wp.com/www.zeldman.com/wp-content/Google-Chromesnaps003.png"><img src="https://i0.wp.com/www.zeldman.com/wp-content/Google-Chromesnaps003.png?w=640" alt="The Web Standards Project – a liquid layout as seen on a wide computer screen." data-recalc-dims="1" /></a></p>
  71. <p><em>Fig 1. The Web Standards Project: a liquid layout as seen on a wide computer screen. Designed by Andy Clarke in the early 2000s.</em></p>
  72. <p>&nbsp;</p>
  73. <p><a href="https://i0.wp.com/www.zeldman.com/wp-content/Google-Chromesnaps001.png"><img class="softinset" src="https://i0.wp.com/www.zeldman.com/wp-content/Google-Chromesnaps001.png?resize=421%2C1369" alt="" data-recalc-dims="1" /></a></p>
  74. <p><em>Fig 2. The Web Standards Project: a liquid layout as seen on a narrow computer screen. On the narrow screen, type overlaps and the page becomes unusable.</em></p>
  75. <p>&nbsp;</p>
  76. <p id="03de" class="graf graf--p graf-after--figure">Ugly on one side. Unusable on the other. It took a special breed of designer to forge ahead with Liquid Layout anyway.</p>
  77. <p id="a688" class="graf graf--p graf-after--p">Were it were not for the iPhone and the phones and tablets that rose quickly in its wake, the W3C would likely not have invented breakpoints. And without breakpoints, there could be no Responsive Web Design. And without Responsive Web Design, created by <a class="markup--anchor markup--p-anchor" href="https://ethanmarcotte.com/" target="_blank" rel="nofollow noopener" data-href="https://ethanmarcotte.com/"><strong class="markup--strong markup--p-strong">a visually gifted designer</strong></a> and with tools to satisfy his peers, the idea that drove Liquid design back in the 1990s would not, at long last, have caught on.</p>
  78. <p id="8577" class="graf graf--p graf-after--p">It’s easy to view our current design thinking as more evolved than what we practiced in the past. And in some ways, it is. But if you read between the lines, it’s fair to say that our thinking was always advanced. It’s only now that our tools are beginning to catch up.</p>
  79. <h4>Read more about Liquid and Responsive Web Design</h4>
  80. <ul>
  81. <li><a href="https://alistapart.com/article/dao">A Dao of Web Design</a> by John Allsopp, <em>A List Apart</em>, April 2000</li>
  82. <li><a href="https://web.archive.org/web/20040701041831/http://www.digital-web.com/articles/liquid_web_design/ ">Liquid Web Design: Build it right and it will work no matter what the container</a>, by Nick Finck, <em class="markup--em markup--li-em">Digital Web</em>, August 1999</li>
  83. <li><a href="https://web.archive.org/web/20040701041831/http://www.digital-web.com/articles/liquid_web_design/">What is Liquid Design?</a> By Nick Wilson, November 2002</li>
  84. <li><a href="http://trentwalton.com/2013/01/07/flexible-foundations/">Flexible Foundations</a> by Trent Walton, 2013</li>
  85. </ul>
  86. <p>&nbsp;</p>
  87. <p>☞ <em class="markup--em markup--p-em">Illustration by </em><a class="markup--anchor markup--p-anchor" href="https://twitter.com/pseudoroom/" target="_blank" rel="nofollow noopener" data-href="https://twitter.com/pseudoroom/"><em class="markup--em markup--p-em">Justin Dauer</em></a><em class="markup--em markup--p-em">. Follow me </em><a class="markup--anchor markup--p-anchor" href="https://twitter.com/zeldman" target="_blank" rel="nofollow noopener nofollow noopener nofollow noopener nofollow noopener noopener noopener nofollow noopener noopener nofollow noopener nofollow noopener nofollow noopener nofollow noopener noopener noopener nofollow noopener noopener nofollow noopener" data-href="https://twitter.com/zeldman"><em class="markup--em markup--p-em">@zeldman</em></a><em class="markup--em markup--p-em">. A version of this article appears on <a href="https://medium.com/@zeldman/a-dao-of-responsive-liquid-d49c74fc87d1">Medium</a>. The 11th Annual <a href="http://bluebeanieday.tumblr.com">Blue Beanie Day</a> in support of web standards takes place November 30 on the internet.</em></p>
  88. <p>&nbsp;</p>
  89. <p><span style="border-top-left-radius: 2px; border-top-right-radius: 2px; border-bottom-right-radius: 2px; border-bottom-left-radius: 2px; text-indent: 20px; width: auto; padding: 0px 4px 0px 0px; text-align: center; font-style: normal; font-variant-caps: normal; font-weight: bold; font-stretch: normal; font-size: 11px; line-height: 20px; font-family: 'Helvetica Neue', Helvetica, sans-serif; color: #ffffff; background-image: url(data:image/svg+xml; base64,phn2zyb4bwxucz0iahr0cdovl3d3dy53my5vcmcvmjawmc9zdmciighlawdodd0imzbwecigd2lkdgg9ijmwchgiihzpzxdcb3g9ii0xic0xidmxidmxij48zz48cgf0acbkpsjnmjkundq5lde0ljy2mibdmjkundq5ldiyljcymiaymi44njgsmjkumju2ide0ljc1ldi5lji1nibdni42mzismjkumju2idaumduxldiyljcymiawlja1mswxnc42njigqzaumduxldyunjaxidyunjmyldaumdy3ide0ljc1ldaumdy3iemymi44njgsmc4wnjcgmjkundq5ldyunjaxidi5ljq0oswxnc42njiiigzpbgw9iinmzmyiihn0cm9rzt0ii2zmziigc3ryb2tllxdpzhropsixij48l3bhdgg+phbhdgggzd0itte0ljczmywxljy4nibdny41mtysms42odygms42njusny40otugms42njusmtqunjyyiemxljy2nswymc4xntkgns4xmdksmjquodu0idkuotcsmjyunzq0iem5ljg1niwyns43mtggos43ntmsmjqumtqzidewljaxniwymy4wmjigqzewlji1mywymi4wmsaxms41ndgsmtyuntcyidexlju0ocwxni41nzigqzexlju0ocwxni41nzigmteumtu3lde1ljc5nsaxms4xntcsmtqunjq2iemxms4xntcsmtiuodqyideyljixmswxms40otugmtmuntiyldexljq5nsbdmtqunjm3ldexljq5nsaxns4xnzusmtiumzi2ide1lje3nswxmy4zmjmgqze1lje3nswxnc40mzygmtqundyylde2ljegmtqumdkzlde3ljy0mybdmtmunzg1lde4ljkznsaxnc43ndusmtkuotg4ide2ljayocwxos45odggqze4ljm1mswxos45odggmjaumtm2lde3lju1niaymc4xmzysmtqumdq2iemymc4xmzysmtauotm5ide3ljg4ocw4ljc2nyaxnc42nzgsoc43njcgqzewljk1osw4ljc2nya4ljc3nywxms41mzygoc43nzcsmtqumzk4iem4ljc3nywxns41mtmgos4ymswxni43mdkgos43ndksmtcumzu5iem5ljg1niwxny40odggos44nzismtcunia5ljg0lde3ljczmsbdos43ndesmtgumtqxidkuntismtkumdizidkundc3lde5ljiwmybdos40miwxos40nca5lji4ocwxos40otegos4wncwxos4znzygqzcunda4lde4ljyymia2ljm4nywxni4yntigni4zodcsmtqumzq5iem2ljm4nywxmc4yntygos4zodmsni40otcgmtuumdiyldyundk3iemxos41ntusni40otcgmjmumdc4ldkunza1idizlja3ocwxmy45otegqzizlja3ocwxoc40njmgmjaumjm5ldiylja2miaxni4yotcsmjiumdyyiemxnc45nzmsmjiumdyyidezljcyocwyms4znzkgmtmumzayldiwlju3mibdmtmumzayldiwlju3miaxmi42ndcsmjmumdugmtiundg4ldizljy1nybdmtiumtkzldi0ljc4ncaxms4zotysmjyumtk2idewljg2mywyny4wntggqzeylja4niwyny40mzqgmtmumzg2ldi3ljyznyaxnc43mzmsmjcunjm3iemyms45nswyny42mzcgmjcuodaxldixljgyocayny44mdesmtqunjyyiemyny44mdesny40otugmjeuotusms42odygmtqunzmzldeunjg2iibmawxspsijymqwodfjij48l3bhdgg+pc9npjwvc3znpg==); background-size: 14px 14px; background-color: #bd081c; position: absolute; opacity: 1; z-index: 8675309; display: none; cursor: pointer; border: none; -webkit-font-smoothing: antialiased; background-position: 3px 50%; background-repeat: no-repeat no-repeat;">Save</span><span style="border-top-left-radius: 2px; border-top-right-radius: 2px; border-bottom-right-radius: 2px; border-bottom-left-radius: 2px; text-indent: 20px; width: auto; padding: 0px 4px 0px 0px; text-align: center; font-style: normal; font-variant-caps: normal; font-weight: bold; font-stretch: normal; font-size: 11px; line-height: 20px; font-family: 'Helvetica Neue', Helvetica, sans-serif; color: #ffffff; background-image: url(data:image/svg+xml; base64,phn2zyb4bwxucz0iahr0cdovl3d3dy53my5vcmcvmjawmc9zdmciighlawdodd0imzbwecigd2lkdgg9ijmwchgiihzpzxdcb3g9ii0xic0xidmxidmxij48zz48cgf0acbkpsjnmjkundq5lde0ljy2mibdmjkundq5ldiyljcymiaymi44njgsmjkumju2ide0ljc1ldi5lji1nibdni42mzismjkumju2idaumduxldiyljcymiawlja1mswxnc42njigqzaumduxldyunjaxidyunjmyldaumdy3ide0ljc1ldaumdy3iemymi44njgsmc4wnjcgmjkundq5ldyunjaxidi5ljq0oswxnc42njiiigzpbgw9iinmzmyiihn0cm9rzt0ii2zmziigc3ryb2tllxdpzhropsixij48l3bhdgg+phbhdgggzd0itte0ljczmywxljy4nibdny41mtysms42odygms42njusny40otugms42njusmtqunjyyiemxljy2nswymc4xntkgns4xmdksmjquodu0idkuotcsmjyunzq0iem5ljg1niwyns43mtggos43ntmsmjqumtqzidewljaxniwymy4wmjigqzewlji1mywymi4wmsaxms41ndgsmtyuntcyidexlju0ocwxni41nzigqzexlju0ocwxni41nzigmteumtu3lde1ljc5nsaxms4xntcsmtqunjq2iemxms4xntcsmtiuodqyideyljixmswxms40otugmtmuntiyldexljq5nsbdmtqunjm3ldexljq5nsaxns4xnzusmtiumzi2ide1lje3nswxmy4zmjmgqze1lje3nswxnc40mzygmtqundyylde2ljegmtqumdkzlde3ljy0mybdmtmunzg1lde4ljkznsaxnc43ndusmtkuotg4ide2ljayocwxos45odggqze4ljm1mswxos45odggmjaumtm2lde3lju1niaymc4xmzysmtqumdq2iemymc4xmzysmtauotm5ide3ljg4ocw4ljc2nyaxnc42nzgsoc43njcgqzewljk1osw4ljc2nya4ljc3nywxms41mzygoc43nzcsmtqumzk4iem4ljc3nywxns41mtmgos4ymswxni43mdkgos43ndksmtcumzu5iem5ljg1niwxny40odggos44nzismtcunia5ljg0lde3ljczmsbdos43ndesmtgumtqxidkuntismtkumdizidkundc3lde5ljiwmybdos40miwxos40nca5lji4ocwxos40otegos4wncwxos4znzygqzcunda4lde4ljyymia2ljm4nywxni4yntigni4zodcsmtqumzq5iem2ljm4nywxmc4yntygos4zodmsni40otcgmtuumdiyldyundk3iemxos41ntusni40otcgmjmumdc4ldkunza1idizlja3ocwxmy45otegqzizlja3ocwxoc40njmgmjaumjm5ldiylja2miaxni4yotcsmjiumdyyiemxnc45nzmsmjiumdyyidezljcyocwyms4znzkgmtmumzayldiwlju3mibdmtmumzayldiwlju3miaxmi42ndcsmjmumdugmtiundg4ldizljy1nybdmtiumtkzldi0ljc4ncaxms4zotysmjyumtk2idewljg2mywyny4wntggqzeylja4niwyny40mzqgmtmumzg2ldi3ljyznyaxnc43mzmsmjcunjm3iemyms45nswyny42mzcgmjcuodaxldixljgyocayny44mdesmtqunjyyiemyny44mdesny40otugmjeuotusms42odygmtqunzmzldeunjg2iibmawxspsijymqwodfjij48l3bhdgg+pc9npjwvc3znpg==); background-size: 14px 14px; background-color: #bd081c; position: absolute; opacity: 1; z-index: 8675309; display: none; cursor: pointer; border: none; -webkit-font-smoothing: antialiased; background-position: 3px 50%; background-repeat: no-repeat no-repeat;">Save</span></p>
  90. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/11/19/dao-responsive-liquid/">A Dao of Responsive Liquid</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  91. ]]></content:encoded>
  92. <post-id xmlns="com-wordpress:feed-additions:1">14596</post-id> </item>
  93. <item>
  94. <title>Advice for designers</title>
  95. <link>http://www.zeldman.com/2017/11/06/advice-for-designers/</link>
  96. <pubDate>Mon, 06 Nov 2017 14:17:10 +0000</pubDate>
  97. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  98. <category><![CDATA[Design]]></category>
  99.  
  100. <guid isPermaLink="false">http://www.zeldman.com/?p=14594</guid>
  101. <description><![CDATA[<p>Start by asking questions. Sketch, share your sketches, ask more questions. Don’t be precious with your work. Don’t hurry to finish.</p>
  102. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/11/06/advice-for-designers/">Advice for designers</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  103. ]]></description>
  104. <content:encoded><![CDATA[<img src="http://www.zeldman.com/wp-content/themes/zeldman/images/default.svg" class="lede" alt="" /><p>Start by asking questions. Sketch, share your sketches, ask more questions. Don’t be precious with your work. Don’t hurry to finish.</p>
  105. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/11/06/advice-for-designers/">Advice for designers</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  106. ]]></content:encoded>
  107. <post-id xmlns="com-wordpress:feed-additions:1">14594</post-id> </item>
  108. <item>
  109. <title>Why don’t nonprofit sites convert?</title>
  110. <link>http://www.zeldman.com/2017/09/18/dont-nonprofit-sites-convert/</link>
  111. <pubDate>Mon, 18 Sep 2017 19:08:57 +0000</pubDate>
  112. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  113. <category><![CDATA[Best practices]]></category>
  114. <category><![CDATA[business]]></category>
  115. <category><![CDATA[Design]]></category>
  116. <category><![CDATA[Usability]]></category>
  117. <category><![CDATA[User Experience]]></category>
  118. <category><![CDATA[UX]]></category>
  119.  
  120. <guid isPermaLink="false">http://www.zeldman.com/?p=14588</guid>
  121. <description><![CDATA[<p>Living in New York and working in media, I talk to nonprofit organizations a lot. Big or small, they all say the same. No matter how much work they put into their apps and websites, they just don’t get enough new members. No matter how many expensive redesigns they undertake, they still don’t convert. Why [&#8230;]</p>
  122. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/09/18/dont-nonprofit-sites-convert/">Why don’t nonprofit sites convert?</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  123. ]]></description>
  124. <content:encoded><![CDATA[<img src="http://www.zeldman.com/wp-content/themes/zeldman/images/default.svg" class="lede" alt="" /><p>Living in New York and working in media, I talk to nonprofit organizations <em>a lot</em>. Big or small, they all say the same. No matter how much work they put into their apps and websites, they just don’t get enough new members. No matter how many expensive redesigns they undertake, they still don’t convert. Why is this?</p>
  125. <p>Generally, it’s the same reason any site with a great product doesn’t convert: the organization spends too much time and effort on the pages and sections that matter to the organization, and too little on the interactions that matter to the member. (“Member” is <em>NGOese</em> for customer.)</p>
  126. <p>Of course there are sites that don’t convert because they have a crappy product. Or an inappropriately priced product. Or because their content attracts people who are never going to be their customers, and gets missed by people who might want what they’re selling. Or because their content attracts nobody. Failure has a thousand fathers, and most businesses fail, so the fact that a website doesn’t convert could mean almost anything. (To know what it actually means, you need data, and you need to watch users interact with it.)</p>
  127. <p>But with nonprofit sites, the product is almost always great, and the person visiting is almost always interested. So what goes wrong?</p>
  128. <h3>Never mind the user, here’s the About page</h3>
  129. <p>What goes wrong is that nonprofit stakeholders are so passionate about their mission—a passion that only deepens, the longer they work there—that they design an experience which reflects their passion for the mission, instead of one which maps to a member’s mental model. </p>
  130. <p>NGOs lavish attention on their About page and mission statement and forget to work on their members’ immediate, transactional needs. And this is true even for those members who are as passionate about the cause, in their own way, as the stakeholders are in theirs. In the wake of a hurricane, a passionate member thinks of your site in hopes of donating food or giving blood. But nothing on the site calls out to that member and addresses her needs. All she sees are menus, headlines, and buttons trying to lead her to what matters to the organization — namely, the things it says about itself.</p>
  131. <h3>How to satisfy the user and convert at the same time</h3>
  132. <p>First, decide what one single action you, as the organization, want the user to perform. Should they sign up for your mailing list? Make a donation? Keep it singular, and make it simple. One form field to fill out is better than two; two is better than four.</p>
  133. <p>Next, put yourself in the member’s shoes. What does that member wish to achieve on your website? Have you created transactions and content that allow her to do what she came to do? Have you designed and written menus, links, and headlines that help her find the content that matters to her? Forget the organization, for now. Pretend the only thing that matters is what the user wants. (Because, ultimately, it is.)</p>
  134. <p>Do these things, and weave your singular, simple conversion opportunity into each screen sequence with which your user interacts. To optimize your chance of success, <strong>place the conversion opportunity at the very point where the user successfully finishes transacting the business that mattered to her</strong>. Not before (where it is only a distraction). Not in another part of the site (which she has no interest in visiting). She’s a lot likelier to sign up for your mailing list after you’ve helped her donate food to her neighbors than she is to sign up in an unsolicited popup window.</p>
  135. <h3>Thank you, Captain Obvious</h3>
  136. <p>All the above suggestions are obvious common sense, and have been known since transactional web design was in its infancy in the 1990s. And yet, because of organizational dynamics, internal politics, and our getting so close to our own material that our eyes go out of focus, we forget these simple ideas more often than we use them—and fail when success is so easy, and so close to hand.</p>
  137. <hr />
  138. <p><em>I’ll be leading a panel discussion, <a href="https://www.meetup.com/Nonprofits-That-Code/events/242196820/">Dispatches from the Future: Nonprofits and Tech</a>, on Wednesday, 20 September, in Brooklyn.</em></p>
  139. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/09/18/dont-nonprofit-sites-convert/">Why don’t nonprofit sites convert?</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  140. ]]></content:encoded>
  141. <post-id xmlns="com-wordpress:feed-additions:1">14588</post-id> </item>
  142. <item>
  143. <title>Medium to pay writers; program similar to Readability</title>
  144. <link>http://www.zeldman.com/2017/08/23/medium-pay-writers-program-similar-readability/</link>
  145. <pubDate>Wed, 23 Aug 2017 16:53:11 +0000</pubDate>
  146. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  147. <category><![CDATA[Advertising]]></category>
  148. <category><![CDATA[content]]></category>
  149. <category><![CDATA[Design]]></category>
  150. <category><![CDATA[Publications]]></category>
  151. <category><![CDATA[Publishing]]></category>
  152.  
  153. <guid isPermaLink="false">http://www.zeldman.com/?p=14576</guid>
  154. <description><![CDATA[<p>INTERESTING. Medium will now pay writers. The revenue to pay writers will derive, not from advertising—Medium scorns it—but from member contributions. How Medium will pay writers Medium now publishes two kinds of content: public content, viewable by anyone; and private, members-only content. Medium members pay a small monthly fee; in return they get access to [&#8230;]</p>
  155. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/08/23/medium-pay-writers-program-similar-readability/">Medium to pay writers; program similar to Readability</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  156. ]]></description>
  157. <content:encoded><![CDATA[<img src="http://www.zeldman.com/wp-content/themes/zeldman/images/default.svg" class="lede" alt="" /><p>INTERESTING. <a href="https://blog.medium.com/expanding-the-medium-partner-program-3be09dd146e4">Medium will now pay writers</a>. The revenue to pay writers will derive, not from advertising—Medium scorns it—but from member contributions.</p>
  158. <h3>How Medium will pay writers</h3>
  159. <p>Medium now publishes two kinds of content: public content, viewable by anyone; and private, members-only content. Medium members pay a small monthly fee; in return they get access to members-only content.</p>
  160. <p>As in the past, writers who write public content will not be paid, but they will have access to a potentially large audience. Only writers who write members-only content will have the potential to earn.</p>
  161. <p>Payments will be based on “<a href="https://help.medium.com/hc/en-us/articles/115011350967-Claps">claps</a>,” a UI experiment Medium introduced seemingly only a few days ago; readers are supposed to indicate how much they like a story by how hard (or how long) they press on the clap widget. None of this is explained to readers in context, but it’s pretty easy to figure out. At least, it is easy to figure out that clapping indicates approval, and that the longer you lean on the clapper, the higher the numeric approval level you can share.</p>
  162. <p>The “clap” widget also appears on public stories, where it has no effect on how much the author will get paid—since writers of public stories will not get paid. On public stories, it’s just there for fun, and/or the make the author feel good. You can’t clap for your own story, which helps prevent the most obvious types of system gaming.</p>
  163. <p>Initially, the payment program will be open only to a select group of writers, but if it succeeds, more and more writers will be included.</p>
  164. <h3>Why it matters</h3>
  165. <p>As the publisher of <a href="https://alistapart.com/">A List Apart</a>, which has relied on advertising revenue in the past but is about to stop doing that; as a writer, reader, and passionate devotee of web-delivered content; and as a blogger at zeldman.com since 1995, I will be watching this experiment and hoping for its success. I became a Medium member as soon as the publication offered it, even though I have no interest in reading “exclusive,” members-only content. I did it to support Medium, which I see as <a href="https://twitter.com/ev">one web pioneer</a>’s attempt to keep the web a vital content ecosystem.</p>
  166. <p>It’s the same reason I cheered for the <a href="https://www.readability.com/">Readability</a> app invented by my friend Rich Ziade and his team, back in the day. I even served on Readability’s advisory board, for which I was paid—and asked—nothing. I did it because I believed in Readability’s mission to find a way to pay for content. That particular experiment died, but in many ways its spirit lives on in Medium, whose readable visual layout Readability helped to inspire.</p>
  167. <p>I will not apply to be a paid Medium writer since I have my own magazine’s content and finances to figure out, and since I choose to publish my content publicly. But I applaud what Ev and his teammates are doing, and I will be watching.</p>
  168. <p>Source: <em><a href="https://blog.medium.com/expanding-the-medium-partner-program-3be09dd146e4">Expanding the Medium Partner Program – 3 min read</a></em></p>
  169. <p><em><a href="https://medium.com/@zeldman/medium-to-pay-writers-program-similiar-to-readability-421a09ead923">Also published on Medium</a>.</em></p>
  170. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/08/23/medium-pay-writers-program-similar-readability/">Medium to pay writers; program similar to Readability</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  171. ]]></content:encoded>
  172. <post-id xmlns="com-wordpress:feed-additions:1">14576</post-id> </item>
  173. <item>
  174. <title>It’s just lunch.</title>
  175. <link>http://www.zeldman.com/2017/08/08/reconnecting-with-former-clients-design-problem-lets-talk/</link>
  176. <pubDate>Tue, 08 Aug 2017 12:16:30 +0000</pubDate>
  177. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  178. <category><![CDATA[business]]></category>
  179. <category><![CDATA[Design]]></category>
  180.  
  181. <guid isPermaLink="false">http://www.zeldman.com/?p=14559</guid>
  182. <description><![CDATA[<p>I HADN’T heard from her in years. Suddenly, there she was in my in-box. Tentatively proposing coffee. Maybe lunch. A dam broke inside me, releasing a flood of warm memories. Our first, tentative contact ten years or more ago. Getting to know each other. Endless, happy discussions about where this thing was going. Coming together [&#8230;]</p>
  183. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/08/08/reconnecting-with-former-clients-design-problem-lets-talk/">It’s just lunch.</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  184. ]]></description>
  185. <content:encoded><![CDATA[<p><img src="https://i0.wp.com/www.zeldman.com/wp-content/ramen.jpg?w=640" alt="A nice bowl of ramen." class="lead" data-recalc-dims="1" /></p>
  186. <p>I HADN’T heard from her in years. Suddenly, there she was in my in-box. Tentatively proposing coffee. Maybe lunch. A dam broke inside me, releasing a flood of warm memories. Our first, tentative contact ten years or more ago. Getting to know each other. Endless, happy discussions about where this thing was going. Coming together on goals and brand; on voice and tone. Finally, the joy of designing and launching her website. And then, abruptly, the last invoice and the hurried departure.</p>
  187. <p>My former client. She had a new job now. She wanted to catch up. And, sheepishly, she admitted, she might want something more. Advice about a design problem.</p>
  188. <p>Over an unassuming wooden table laden with summer lunch—mine was Ramen, hers was salad—we shared personal updates. Kids, relationships, projects. And then we got down to the real agenda: an issue at work that was stumping her. Desire for an outside perspective.</p>
  189. <p>Former clients often feel slightly embarrassed about reaching out for a little free advice. They shouldn’t. As a designer, one of my greatest joys is to reconnect with good people whose projects I loved working on. <a href="https://abookapart.com/products/design-is-a-job"><span class="s2">Design is a job</span></a>, but it’s also a relationship. When design is going well, the exchange of ideas is almost addictively exciting. And then, all too soon, the project ends, and, if you’re a consulting designer, and you’re lucky enough to have a steady stream of business, you move on to the next gig.</p>
  190. <p>We designers have built-in forgetters: super powers that enable us to care passionately about the problem we’re solving and the people we’re solving it for, and then, absurdly, to discard those feelings as we move on to the next client and design problem.</p>
  191. <p>Clients have a built-in forgetter too. They forget that our relationship, although partly monetary, was also very real. Many clients are self-conscious about reconnecting personally and asking for a small favor in the same breath. But I couldn’t welcome that more. If I can help people, it’s a joy to me. Collaborating on the discovery and solution to a problem isn’t just a stimulating mental exercise and a profession: it’s also a codependent rush.</p>
  192. <p class="p1"><span class="s1">Between the cracks of <a href="https://studio.zeldman.com/"><span class="s2">my studio</span></a>’s bigger projects, I’m always looking for ways to help people. So, in the spirit of <a href="https://alistapart.com/event/drweb"><span class="s2">Ask Dr Web</span></a>, I&#8217;m taking this opportunity to issue an invitation to folks located in or visiting New York. If you’re someone in my network—a former client or old friend or both—with a design problem to mull over, you don’t have to do the mulling alone. Ping me. And let’s do lunch.</span></p>
  193. <p>
  194. <i><a href="https://medium.com/@zeldman/its-just-lunch-e68b7938199d">Also published on Medium</a>.</i></p>
  195. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/08/08/reconnecting-with-former-clients-design-problem-lets-talk/">It’s just lunch.</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  196. ]]></content:encoded>
  197. <post-id xmlns="com-wordpress:feed-additions:1">14559</post-id> </item>
  198. <item>
  199. <title>Big Web Show № 159: If You Can’t Stand the Heatmaps, Stay Out of the Conversion, with @nickd</title>
  200. <link>http://www.zeldman.com/2017/06/16/big-web-show-%e2%84%96-159-cant-stand-heatmaps-stay-conversion-nickd/</link>
  201. <pubDate>Fri, 16 Jun 2017 16:36:25 +0000</pubDate>
  202. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  203. <category><![CDATA[Best practices]]></category>
  204. <category><![CDATA[Blogs and Blogging]]></category>
  205. <category><![CDATA[business]]></category>
  206. <category><![CDATA[client services]]></category>
  207. <category><![CDATA[clients]]></category>
  208. <category><![CDATA[Design]]></category>
  209. <category><![CDATA[The Big Web Show]]></category>
  210. <category><![CDATA[User Experience]]></category>
  211. <category><![CDATA[UX]]></category>
  212.  
  213. <guid isPermaLink="false">http://www.zeldman.com/?p=14551</guid>
  214. <description><![CDATA[<p>NICK Disabato (@nickd) and I discuss heat maps, conversion rates, design specialization, writing for the web, Jakob Nielsen, and the early days of blogging in Episode № 159 of The Big Web Show – “everything web that matters.” Listen and enjoy. Sponsored by ZipRecruiter, Blue Apron, User Interviews, and Hotjar. URLS nickd.org/bio/ draft.nu/ nickd.org/ twitter.com/nickd</p>
  215. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/06/16/big-web-show-%e2%84%96-159-cant-stand-heatmaps-stay-conversion-nickd/">Big Web Show № 159: If You Can’t Stand the Heatmaps, Stay Out of the Conversion, with @nickd</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  216. ]]></description>
  217. <content:encoded><![CDATA[<p><a href="http://5by5.tv/bigwebshow/159"><img src="https://i1.wp.com/www.zeldman.com/wp-content/nickd.jpg?w=640" alt="Nick Disabato AKA @nickd" data-recalc-dims="1" /></a></p>
  218. <p class="intro">NICK Disabato (@nickd) and I discuss heat maps, conversion rates, design specialization, writing for the web, Jakob Nielsen, and the early days of blogging in <a href="http://5by5.tv/bigwebshow/159">Episode № 159</a> of The Big Web Show – “everything web that matters.” Listen and enjoy.</p>
  219. <p>Sponsored by <a href="https://www.ziprecruiter.com/bigwebshow">ZipRecruiter</a>, <a href="https://www.blueapron.com/bigwebshow">Blue Apron</a>, <a href="https://www.userinterviews.com/bigwebshow">User Interviews</a>, and <a href="https://hotjar.com/bigwebshow">Hotjar</a>.</p>
  220. <h3>URLS</b></h3>
  221. <ul>
  222. <li><a href="http://nickd.org/bio/">nickd.org/bio/</a></li>
  223. <li><a href="https://draft.nu/">draft.nu/</a></li>
  224. <li><a href="http://nickd.org/">nickd.org/</a></li>
  225. <li><a href="https://twitter.com/nickd">twitter.com/nickd</a></li>
  226. </ul>
  227. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/06/16/big-web-show-%e2%84%96-159-cant-stand-heatmaps-stay-conversion-nickd/">Big Web Show № 159: If You Can’t Stand the Heatmaps, Stay Out of the Conversion, with @nickd</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  228. ]]></content:encoded>
  229. <post-id xmlns="com-wordpress:feed-additions:1">14551</post-id> </item>
  230. <item>
  231. <title>Buy a piece of studio.zeldman</title>
  232. <link>http://www.zeldman.com/2017/05/12/buy-piece-studio-zeldman/</link>
  233. <pubDate>Fri, 12 May 2017 19:59:06 +0000</pubDate>
  234. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  235. <category><![CDATA[A Space Apart]]></category>
  236. <category><![CDATA[business]]></category>
  237. <category><![CDATA[Design]]></category>
  238. <category><![CDATA[New York City]]></category>
  239. <category><![CDATA[NYC]]></category>
  240. <category><![CDATA[Products]]></category>
  241. <category><![CDATA[studio.zeldman]]></category>
  242. <category><![CDATA[zeldman.com]]></category>
  243.  
  244. <guid isPermaLink="false">http://www.zeldman.com/?p=14540</guid>
  245. <description><![CDATA[<p>We’ve got some exciting news to share. Web and interaction design studio.zeldman is moving, from our digs at 148 Madison Avenue to a new location on Fifth Avenue. As of June 1, we’ll be designing, creating, and consulting out of our beautiful new studio space at The Yard: Flatiron North. Closing our co-working design studio [&#8230;]</p>
  246. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/05/12/buy-piece-studio-zeldman/">Buy a piece of studio.zeldman</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  247. ]]></description>
  248. <content:encoded><![CDATA[<p><a href="https://vr.zeldman.com/"><img src="https://i0.wp.com/cdn-images-1.medium.com/max/600/1*JzJoBcUa_Z4LD64H3AAxvg.jpeg?w=640&#038;ssl=1" alt="Jessica Hische enjoys the ball chair at A Space Apart." data-image-id="1*JzJoBcUa_Z4LD64H3AAxvg.jpeg" data-recalc-dims="1" /></a></p>
  249. <p class="graf graf--p">We’ve got some exciting news to share. Web and interaction design <a class="markup--anchor markup--p-anchor" href="https://studio.zeldman.com/" target="_blank" rel="noopener noreferrer" data-href="https://studio.zeldman.com/">studio.zeldman</a> is moving, from <a href="https://vr.zeldman.com/">our digs</a> at 148 Madison Avenue to a new location on Fifth Avenue. As of June 1, we’ll be designing, creating, and consulting out of our beautiful new studio space at <a class="markup--anchor markup--p-anchor" href="https://theyard.nyc/locations/flatiron-north/" target="_blank" rel="noopener noreferrer" data-href="https://theyard.nyc/locations/flatiron-north/">The Yard: Flatiron North</a>.</p>
  250. <h3>Closing our co-working design studio</h3>
  251. <p class="graf graf--p">This means we’re closing<a class="markup--anchor markup--p-anchor" href="https://www.flickr.com/photos/zeldman/albums/72157628836818769" target="_blank" rel="noopener noreferrer" data-href="https://www.flickr.com/photos/zeldman/albums/72157628836818769"> A Space Apart</a>, the Madison Avenue co-working design studio we opened in January, 2012. A Space Apart was a fun experiment, and we loved learning from the design studios, product companies, publications and startups with whom we shared it. Companies like <a class="markup--anchor markup--p-anchor" href="http://fontbureau.typenetwork.com/" target="_blank" rel="noopener noreferrer" data-href="http://fontbureau.typenetwork.com/">Font Bureau</a>, <a class="markup--anchor markup--p-anchor" href="https://monkeydo.biz/" target="_blank" rel="noopener noreferrer" data-href="https://monkeydo.biz/">Monkey Do</a>, <a class="markup--anchor markup--p-anchor" href="http://www.zeldman.com/2016/01/21/sharing-is-caring-the-shopify-partner-studio-program/" target="_blank" rel="noopener noreferrer" data-href="http://www.zeldman.com/2016/01/21/sharing-is-caring-the-shopify-partner-studio-program/">Shopify Partners</a>,<a class="markup--anchor markup--p-anchor" href="http://www.daniloblack.com/" target="_blank" rel="noopener noreferrer" data-href="http://www.daniloblack.com/"> Danilo Black</a>, Been (RIP), <a class="markup--anchor markup--p-anchor" href="http://promediacorp.com/" target="_blank" rel="noopener noreferrer" data-href="http://promediacorp.com/">Promedia</a>, <a class="markup--anchor markup--p-anchor" href="http://www.bytedept.com/" target="_blank" rel="noopener noreferrer" data-href="http://www.bytedept.com/">Byte Dept</a>, <a class="markup--anchor markup--p-anchor" href="http://nicksherman.com/" target="_blank" rel="noopener noreferrer" data-href="http://nicksherman.com/">Nick Sherman</a>, <a class="markup--anchor markup--p-anchor" href="http://fredgatesdesign.co/" target="_blank" rel="noopener noreferrer" data-href="http://fredgatesdesign.co/">Fred Gates Design</a>, <a class="markup--anchor markup--p-anchor" href="https://waywardwild.com/" target="_blank" rel="noopener noreferrer" data-href="https://waywardwild.com/">Wayward Wild</a> and <a class="markup--anchor markup--p-anchor" href="http://thegreatdiscontent.com/" target="_blank" rel="noopener noreferrer" data-href="http://thegreatdiscontent.com/">The Great Discontent</a> and have all shared our water cooler at one time or another during the whirligig of the past five years. Creatively, it’s been amazing.</p>
  252. <p class="graf graf--p">But we’re tired of playing landlord. Instead of debugging the internet router, tending to the recycling, hiring HVAC repair people, and seeking suitable replacement studio mates when a company moves out, we’d rather spend our time solving our clients’ design problems and making cool stuff like <a class="markup--anchor markup--p-anchor" href="https://alistapart.com/" target="_blank" rel="noopener noreferrer" data-href="https://alistapart.com/">A List Apart</a>, <a class="markup--anchor markup--p-anchor" href="https://abookapart.com/" target="_blank" rel="noopener noreferrer" data-href="https://abookapart.com/">A Book Apart</a>, <a class="markup--anchor markup--p-anchor" href="http://5by5.tv/bigwebshow" target="_blank" rel="noopener noreferrer" data-href="http://5by5.tv/bigwebshow">The Big Web Show</a>, and <a class="markup--anchor markup--p-anchor" href="https://aneventapart.com/" target="_blank" rel="noopener noreferrer" data-href="https://aneventapart.com/">An Event Apart</a>. And The Yard’s the perfect place for us to ply our trade and make our goods. (Plus we still get to rub shoulders with other creative business folk.)</p>
  253. <h3>We can’t take it with us: furnish your office with our stuff!</h3>
  254. <p class="graf graf--p">Running a co-working studio space meant buying a lot of furniture and equipment. Beautiful stuff, still in great condition. Elegant stuff, because we’re designers. Stuff we won’t need any more, now that we’re moving to new digs where somebody else does landlord duty. So we’re selling it, for a lot less than we paid. And that’s where (maybe) you come in.</p>
  255. <p class="graf graf--p">Most everything must go, including our famous <a class="markup--anchor markup--p-anchor" href="https://eeroaarnio.com/products/chairs/ball-chair/" target="_blank" rel="noopener noreferrer" data-href="https://eeroaarnio.com/products/chairs/ball-chair/">Eero Aarnio (style) ball chair</a> (if its red cushions could talk!), custom Bo Concept shelving, <a class="markup--anchor markup--p-anchor" href="http://www.dwr.com/workspace-desks-tables/eames-desk-unit-edu/1366.html?lang=en_US" target="_blank" rel="noopener noreferrer" data-href="http://www.dwr.com/workspace-desks-tables/eames-desk-unit-edu/1366.html?lang=en_US">Eames Desk Units</a> from Design Within Reach, Herman Miller Aeron chairs (ditto), midcentury tulip table and side chairs, black glass desks, Nespresso espresso maker, file cabinets, icemaker, microwave oven, see-through glass mini-fridge, and more. These are beautiful things that inspire good design, and they deserve good homes.</p>
  256. <p class="graf graf--p"><span style="font-weight: 400;">View all our goods and prices—and even order the ones you want!—via this lovely </span><a href="https://vr.zeldman.com/"><span style="font-weight: 400;">WebVR Walk-through</span></a><span style="font-weight: 400;"> prepared by our own </span><a href="https://studio.zeldman.com/about/roland-dubois/"><span style="font-weight: 400;">Roland Dubois</span></a><span style="font-weight: 400;">. (If you&#8217;re not into the whole WebVR thing, you can also just </span><a href="https://marketplace.apartmenttherapy.com/studiozeldman"><span style="font-weight: 400;">browse our store at Apartment Therapy</span></a><span style="font-weight: 400;">. The VR experience also links directly to the store items, so you&#8217;re good either way.)</span></p>
  257. <p class="graf graf--p"><span style="font-weight: 400;">We leave May 31, and these goods are first-come, first-served, so don’t wait too long. Grab your piece of web and interaction design history today.</span></p>
  258. <p class="graf graf--p">
  259. <p class="graf graf--p">☛  <a href="https://medium.com/@zeldman/buy-a-piece-of-studio-zeldman-96b5cf5d1cd1"><em>Also published at Medium</em></a></p>
  260. <p class="graf graf--p">
  261. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/05/12/buy-piece-studio-zeldman/">Buy a piece of studio.zeldman</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  262. ]]></content:encoded>
  263. <post-id xmlns="com-wordpress:feed-additions:1">14540</post-id> </item>
  264. <item>
  265. <title>Big Web Show № 158: Old Men Shake Fists at the Cloud – with Jim Coudal</title>
  266. <link>http://www.zeldman.com/2017/05/05/big-web-show-%e2%84%96-158-old-men-shake-fists-cloud-jim-coudal/</link>
  267. <pubDate>Fri, 05 May 2017 21:32:04 +0000</pubDate>
  268. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  269. <category><![CDATA[Big Web Show]]></category>
  270. <category><![CDATA[business]]></category>
  271. <category><![CDATA[Design]]></category>
  272. <category><![CDATA[Designers]]></category>
  273. <category><![CDATA[The Big Web Show]]></category>
  274.  
  275. <guid isPermaLink="false">http://www.zeldman.com/?p=14535</guid>
  276. <description><![CDATA[<p>Internet veterans Jim @Coudal &#038; Jeffrey @Zeldman on the death of blogging, the birth of Field Notes, the virtues of a subscription model, and much more. Begins in tears, ends in triumph. One of the most fun (and inspiring) episodes ever.</p>
  277. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/05/05/big-web-show-%e2%84%96-158-old-men-shake-fists-cloud-jim-coudal/">Big Web Show № 158: Old Men Shake Fists at the Cloud – with Jim Coudal</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  278. ]]></description>
  279. <content:encoded><![CDATA[<img src="http://www.zeldman.com/wp-content/themes/zeldman/images/default.svg" class="lede" alt="" /><p>IN <a href="http://5by5.tv/bigwebshow/158">Big Web Show № 158</a>: internet veterans Jim @Coudal &amp; Jeffrey @Zeldman on the death of blogging, the birth of Field Notes, the virtues of a subscription model, and much more. Begins in tears, ends in triumph. One of the most fun (and inspiring) episodes ever. Sponsored by Hotjar &amp; Blue Apron.</p>
  280. <p>Enjoy <a href="http://5by5.tv/bigwebshow/158">Big Web Show № 158</a>.</p>
  281. <h4>URLs</h4>
  282. <p><a href="https://fieldnotesbrand.com/">Field Notes</a><br />
  283. <a href="http://coudal.com/">coudal.com</a><br />
  284. <a href="http://www.coudal.com/video/">coudal video archive</a><br />
  285. <a href="http://www.layertennis.com/">Layer Tennis</a></p>
  286. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/05/05/big-web-show-%e2%84%96-158-old-men-shake-fists-cloud-jim-coudal/">Big Web Show № 158: Old Men Shake Fists at the Cloud – with Jim Coudal</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  287. ]]></content:encoded>
  288. <post-id xmlns="com-wordpress:feed-additions:1">14535</post-id> </item>
  289. <item>
  290. <title>How We Write Proposals in My Design Studio</title>
  291. <link>http://www.zeldman.com/2017/04/11/write-proposals-design-studio/</link>
  292. <pubDate>Wed, 12 Apr 2017 00:05:10 +0000</pubDate>
  293. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  294. <category><![CDATA[business]]></category>
  295. <category><![CDATA[Design]]></category>
  296.  
  297. <guid isPermaLink="false">http://www.zeldman.com/?p=14527</guid>
  298. <description><![CDATA[<p>AS THE HEAD of a newish design studio, I spend a fair amount of time writing proposals. And here’s how I like to do it. I do it like a conversation, and that’s how we start: with phone calls and emails to one or two key decision makers, followed by a research period of about [&#8230;]</p>
  299. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/04/11/write-proposals-design-studio/">How We Write Proposals in My Design Studio</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  300. ]]></description>
  301. <content:encoded><![CDATA[<img src="http://www.zeldman.com/wp-content/themes/zeldman/images/default.svg" class="lede" alt="" /><p>AS THE HEAD of a <a href="https://studio.zeldman.com">newish design studio</a>, I spend a fair amount of time writing proposals. And here’s how I like to do it.</p>
  302. <p>I do it like a conversation, and that’s how we start: with phone calls and emails to one or two key decision makers, followed by a research period of about two to three weeks. And when I say research, what I’m really talking about—besides the usual competitive analysis, analytics, and testing—is even more conversations, but this time with a wider net of stakeholders and customers. </p>
  303. <p>Some studios do this for free, and other studios only do it if the client has signed off on a huge project and paid the first big deposit. But we do this research for a fee. A small, reasonable, consulting fee. If the client then hires us to do the job, we deduct the research fee from the project cost. If they don’t, they’ve gained a lot of great information at a fair cost. (So far, they’ve never not hired us to go on and do the project.)</p>
  304. <h2>From intake to ideas</h2>
  305. <p>About two and half weeks into the research project, we have a strong idea of what matters most to the business and its customers, and we begin to have visions of solutions and innovations, large and small. We can’t help it. We’re interaction designers and it’s how our minds work. </p>
  306. <p>After soaking in a potential client’s world for two-plus weeks, we can’t help beginning to invent designs that solve some of their big and small problems, and that enhance what’s already great about the client and their product. This happens in our heads whether we want it to or not. </p>
  307. <p>At first, we are merely neutral listeners, forcing ourselves not to solve, not to imagine, but only to truly hear and understand. But within about fifteen days, we can’t help but begin imagining little modules and big sections, huge themes and tiny, innovative enhancements, which might please and help our client, their customers, or their staff. And so long as those ideas come from the product, come from what the client and their customers have told us, we feel free to begin sharing them.</p>
  308. <h2>The first design is written </h2>
  309. <p>We do that by writing a report where we share with the client what we’ve begun learning and thinking about their business. Although this report is structured like a business document, we think of it as the first part of design—the first written rough draft of articulating what the client’s business needs to do, and how design might help. </p>
  310. <p>Because it’s a business document, and because we’re workers, not magical pixies, we share facts and data and things stakeholders and customers have said that ring true and that harmonize with other things other stakeholders and customers have said. But all that mustering of facts and data is in the service of a shared creative awakening to the design’s possibilities. </p>
  311. <h2>Start ugly to stay honest</h2>
  312. <p>Now let me tell you how we present our findings: we present them in a Google Doc that the client can access, share, and comment on. We know that many design studios spend much energy visually tarting up even their most basic client communications. Thus, even a humble invoice comes dressed for the prom. </p>
  313. <p>But we don’t do that. We save aesthetics and beauty for the site design. We keep communications open and plain, like an Amish shirt. And we keep communications editable, because this is collaboration, this is conversation, this is not a dead artifact, a take-it-or-leave-it. And Google Docs is the perfect vehicle for it. Just as the traditionally formatted typewritten screenplay is the perfect, neutral vehicle for a writer to share with a director. </p>
  314. <p>This initial research report, this poem of business, this first, rough, written design, presented to the client via the homey simplicity of Google Docs, elicits more client/designer conversation, more emails, more Basecamp posts, more internal discussions in the studio. </p>
  315. <p>And then, after about a week, we present the client with our proposal. Which is clearly the product of all our conversations, and particularly of all the important agreements we reached during that research period. By the time our clients receive the proposal, they are already nodding, as if they always knew what it contained. Because, in a way, they did. Because, if we did our research right, we’ve merely externalized and articulated what they already felt but had not expressed.</p>
  316. <p>And even now, when we’re asking for serious money to do a serious job, we submit our proposal via Google Docs—because prettified, overly branded proposals are about the studio that produces them, whereas our work is about the client and their product. Because even the most painstakingly researched and written proposal, if it is too pretty and too studio-branded, feels like boilerplate, whereas an ugly Google Doc is clearly just work, to be modified or agreed to or argued about.</p>
  317. <p>This is just what we do at our studio. You can try it or not. Personally, I like this approach and I’ve never had a client complain. I’ve always felt a little dirty when presenting a pitch that was too visually polished, and I’ve never won a single gig with boilerplate. Every job has to be earned by studying and understanding and knowing how to share what you’ve understood. At least, that’s how we do it.</p>
  318. <p></p>
  319. <p><em><a href="https://medium.com/alistapart/how-we-write-proposals-in-my-design-studio-20d05977d1e9">Also published on Medium</a>.</em></p>
  320. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/04/11/write-proposals-design-studio/">How We Write Proposals in My Design Studio</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  321. ]]></content:encoded>
  322. <post-id xmlns="com-wordpress:feed-additions:1">14527</post-id> </item>
  323. <item>
  324. <title>A Lucky Fella</title>
  325. <link>http://www.zeldman.com/2017/04/10/a-lucky-fella/</link>
  326. <pubDate>Mon, 10 Apr 2017 19:52:14 +0000</pubDate>
  327. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  328. <category><![CDATA[glamorous]]></category>
  329.  
  330. <guid isPermaLink="false">http://www.zeldman.com/?p=14525</guid>
  331. <description><![CDATA[<p>Cat rearing as a metaphor and the joy of a feces-free tub.</p>
  332. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/04/10/a-lucky-fella/">A Lucky Fella</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  333. ]]></description>
  334. <content:encoded><![CDATA[<img src="http://www.zeldman.com/wp-content/themes/zeldman/images/default.svg" class="lede" alt="" /><p>YESTERDAY I took a bath. Doesn’t sound like much, but it was quite a treat.</p>
  335. <p>I’m staying in a hotel room in Chicago, and there’s a tub here.</p>
  336. <p>I have a tub at home but can never use it, because Snow White, our infantile rescue cat, who wasn’t fully weaned as a kitten, is always sh*tting in our bathtub and p*ssing on our bathroom floor. She has a litter box, and I keep it clean, but that doesn’t matter to her. </p>
  337. <p>Because she was not weaned, she goes through the motions of an adult cat without understanding what they mean—like a Catholic reciting Mass before Vatican II. For instance, after she p*sses on the floor, she bats sand from the litter box all over the floor as well. She knows that sand batting follows p*ssing. She just doesn’t know why. It’s clear to me that her mother tried to teach her how to use a litter box, but she was taken away before the lesson stuck. </p>
  338. <p>To keep our tub at home somewhat clean, I plug it and keep it filled with water. Since cats don’t like water, Snow White refrains from jumping into the tub and sh*tting in it. But the tub is always filled with cold water, which grows dirty over time. You’d think I could drain the tub and bathe in it. But, no.</p>
  339. <p>The tub is hard to plug. Most times, the plug doesn’t work. If I unplug the drain to run a fresh bath, the plug won’t re-plug … water drains silently from the tub, and, while I sleep my innocent sleep, Snow White hops back into the tub and fills it with sh*t. The aromatic, meaty sh*t of cats.</p>
  340. <p>The only way to stop her is to keep the tub plugged and never ever use it. If I think about this, it’s such an overwrought metaphor for so many blocked things in my life, I could scream and never stop.</p>
  341. <p>Instead, I take baths in hotels, when I can, and count myself a lucky fella.</p>
  342. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/04/10/a-lucky-fella/">A Lucky Fella</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  343. ]]></content:encoded>
  344. <post-id xmlns="com-wordpress:feed-additions:1">14525</post-id> </item>
  345. <item>
  346. <title>Love and proposals</title>
  347. <link>http://www.zeldman.com/2017/04/09/love-and-proposals/</link>
  348. <pubDate>Sun, 09 Apr 2017 20:09:54 +0000</pubDate>
  349. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  350. <category><![CDATA[Design]]></category>
  351.  
  352. <guid isPermaLink="false">http://www.zeldman.com/?p=14523</guid>
  353. <description><![CDATA[<p>CHICAGO. Spent my Sunday writing a contract for the ________ design. I find I really enjoy writing proposals. It gives me a chance to see the whole project clearly in my mind, and to demonstrate to clients not just competency but genuine concern for their products and a vision of how to help their business. [&#8230;]</p>
  354. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/04/09/love-and-proposals/">Love and proposals</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  355. ]]></description>
  356. <content:encoded><![CDATA[<img src="http://www.zeldman.com/wp-content/themes/zeldman/images/default.svg" class="lede" alt="" /><p>CHICAGO. Spent my Sunday writing a contract for the ________ design. I find I really enjoy writing proposals. It gives me a chance to see the whole project clearly in my mind, and to demonstrate to clients not just competency but genuine concern for their products and a vision of how to help their business.</p>
  357. <p>Turns out proposal writing can be as creative as anything else we do in design. The only obstacle to overcome is the angry kid inside who doesn’t want to do his homework. If I think of writing the proposal as a damned nuisance, then it is one. But if I view it as an opportunity to test design ideas, that’s what it becomes.</p>
  358. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/04/09/love-and-proposals/">Love and proposals</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  359. ]]></content:encoded>
  360. <post-id xmlns="com-wordpress:feed-additions:1">14523</post-id> </item>
  361. <item>
  362. <title>My Glamorous Life: Crossing the Continent</title>
  363. <link>http://www.zeldman.com/2017/03/31/glamorous-life-crossing-continent/</link>
  364. <pubDate>Sat, 01 Apr 2017 00:04:30 +0000</pubDate>
  365. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  366. <category><![CDATA[An Event Apart]]></category>
  367. <category><![CDATA[glamorous]]></category>
  368.  
  369. <guid isPermaLink="false">http://www.zeldman.com/?p=14520</guid>
  370. <description><![CDATA[<p>RAINY MORNING IN NYC. Put my kid, my ass, and my suitcase in an Uber. Dropped Ava at school, then crawled to JFK via every emergency-vehicle-blocked thoroughfare Lower Manhattan, Brooklyn, and Queens had to offer. The roads were all rain and sirens and nobody getting anywhere. From JFK, flew across the country to surprisingly sunny [&#8230;]</p>
  371. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/03/31/glamorous-life-crossing-continent/">My Glamorous Life: Crossing the Continent</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  372. ]]></description>
  373. <content:encoded><![CDATA[<p><img src="https://i2.wp.com/www.zeldman.com/wp-content/13494182894_2dbb3913db_k.jpg?w=640" alt="The Edgewater Hotel, Seattle, Washington." data-recalc-dims="1" /></p>
  374. <p>RAINY MORNING IN NYC. Put my kid, my ass, and my suitcase in an Uber. Dropped Ava at school, then crawled to JFK via every emergency-vehicle-blocked thoroughfare Lower Manhattan, Brooklyn, and Queens had to offer. The roads were all rain and sirens and nobody getting anywhere.</p>
  375. <p>From JFK, flew across the country to surprisingly sunny Seattle. Now ensconced at the Edgewater, the Robert Mitchum of hotels. Built for the 1962 World’s Fair, it sits at the end of a pier over Puget Sound, perpetually threatening to drown itself, but somehow never going through with it.</p>
  376. <p>The rooms are small, but many face the water. Some boast crow’s-foot tubs and windows over the water. Others, smaller and tub-less, make up for it with a sliding glass door to a tiny patio above the water. Mine is the latter type, and my sliding door is flung wide. Gulls caw and ships pass as I rehearse my AEA presentation and catch up on work.</p>
  377. <p>I brought a sketchbook with me (it was a gift from Ava), and gave Ava a sketchbook before I left. We will draw while we’re apart, and compare drawings when I return to NYC.</p>
  378. <p>Looking forward to seeing friends I’ve not seen in months, and to putting on our <a href="https://aneventapart.com/event/seattle-2017">first AEA show of the year</a>!</p>
  379. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/03/31/glamorous-life-crossing-continent/">My Glamorous Life: Crossing the Continent</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  380. ]]></content:encoded>
  381. <post-id xmlns="com-wordpress:feed-additions:1">14520</post-id> </item>
  382. <item>
  383. <title>Friday Links</title>
  384. <link>http://www.zeldman.com/2017/03/24/friday-links/</link>
  385. <pubDate>Fri, 24 Mar 2017 23:26:21 +0000</pubDate>
  386. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  387. <category><![CDATA[A Book Apart]]></category>
  388. <category><![CDATA[A List Apart]]></category>
  389. <category><![CDATA[An Event Apart]]></category>
  390. <category><![CDATA[Big Web Show]]></category>
  391. <category><![CDATA[Design]]></category>
  392. <category><![CDATA[links]]></category>
  393. <category><![CDATA[The Big Web Show]]></category>
  394.  
  395. <guid isPermaLink="false">http://www.zeldman.com/?p=14512</guid>
  396. <description><![CDATA[<p>TEN great links to launch your weekend: If you missed Gerry McGovern’s brilliant An Event Apart talk on “Top Task Management,” the video’s here for your pleasure. If you missed Eric Meyer’s article “Practical CSS Grid: Adding Grid to an Existing Design” in A List Apart, drop what you’re doing and read! If you missed [&#8230;]</p>
  397. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/03/24/friday-links/">Friday Links</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  398. ]]></description>
  399. <content:encoded><![CDATA[<img src="http://www.zeldman.com/wp-content/themes/zeldman/images/default.svg" class="lede" alt="" /><p class="intro">TEN great links to launch your weekend:</p>
  400. <p>If you missed Gerry McGovern’s brilliant An Event Apart talk on “Top Task Management,” <a href="https://aneventapart.com/news/post/top-task-management-making-it-easier-to-prioritize-by-gerry-mcgovern-AEA">the video’s here</a> for your pleasure.</p>
  401. <p>If you missed Eric Meyer’s article “<a href="https://alistapart.com/article/practical-grid">Practical CSS Grid: Adding Grid to an Existing Design</a>” in <em>A List Apart</em>, drop what you’re doing and read! </p>
  402. <p>If you missed my chat about design discovery with UX consultant Dan Brown on this week’s Big Web Show, <a href="http://5by5.tv/bigwebshow/156">have a listen</a>.</p>
  403. <p>Like it says: “<a href="https://medium.com/alistapart/how-to-build-simple-and-powerful-lazyload-javascript-plugin-34f9f02543c9#.davx028m1">How to Build a Simple and Powerful Lazyload JavaScript Plugin</a>” by Alex Devero in A List Apart: Sidebar.</p>
  404. <p>“<a href="https://trackchanges.postlight.com/modern-javascript-for-ancient-web-developers-58e7cae050f9#.en3ubnlol">Modern JavaScript for Ancient Web Developers</a>” by Gina Trapani in Postlight’s “Track Changes.”</p>
  405. <p>What sex is your font? Many people see typefaces as gendered. All this and much more in “<a href="https://medium.com/@mcpflugie/the-font-purchasing-habits-survey-results-54bb1cd80fe3#.chmngr8bs">The Font Purchasing Habits Survey Results</a>” by Mary Catherine Pflug.</p>
  406. <p>“<a href="http://www.newyorker.com/culture/jia-tolentino/the-gig-economy-celebrates-working-yourself-to-death">The Gig Economy Celebrates Working Yourself to Death</a>” by Jia Tolentino in <em>The New Yorker</em>.</p>
  407. <p>Well, there goes *<em>that</em>* startup idea. <a href="http://www.macworld.com/article/3184018/internet/facebook-starts-warning-us-users-when-theyre-sharing-fake-news.html?idg_eid=350a70e175305fac28923d0622c87080&#038;email_SHA1_lc=21fd735fd1452484d27f79be471d405c94f383b6&#038;cid=mw_nlt_mw_daily_html_2017-03-23">Facebook starts warning U.S. users when they’re sharing fake news</a> in Macworld.</p>
  408. <p>“<a href="https://library.gv.com/the-three-hour-brand-sprint-3ccabf4b768a#.ubvjrcwhn">The Three-Hour Brand Sprint</a>” (“GV’s Simple Recipe For Getting Started On Your Brand”) by Jake Knapp.</p>
  409. <p>“<a href="https://www.fastcodesign.com/3069020/why-are-designers-still-expected-to-take-on-free-work">Why Are Designers Still Expected To Work For Free?</a>” asks <em>Design Observer</em>’s Jessica Helfand in <em>Fast Company</em>’s Co.Design.</p>
  410. <p>Bonus (this one goes to 11): “<a href="https://twitter.com/typethos/status/845281556562247685">Jeffrey Zeldman Presents a Math Problem</a>” from Typethos.</p>
  411. <hr />
  412. <p><em><a href="https://medium.com/let-me-repost-that-for-you-zeldman/friday-links-c349f35b5e1c#.lbep6ploz">Also published in Medium</a>.</em></p>
  413. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/03/24/friday-links/">Friday Links</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  414. ]]></content:encoded>
  415. <post-id xmlns="com-wordpress:feed-additions:1">14512</post-id> </item>
  416. <item>
  417. <title>A Saint Patrick’s Day to remember</title>
  418. <link>http://www.zeldman.com/2017/03/17/saint-patricks-day-remember/</link>
  419. <pubDate>Fri, 17 Mar 2017 16:09:56 +0000</pubDate>
  420. <dc:creator><![CDATA[Jeffrey Zeldman]]></dc:creator>
  421. <category><![CDATA[glamorous]]></category>
  422.  
  423. <guid isPermaLink="false">http://www.zeldman.com/?p=14506</guid>
  424. <description><![CDATA[<p>WHEN my daughter Ava was much younger—about seven—I took her to Toys R Us in Times Square one Saturday that was also Saint Patrick’s Day. You couldn’t ask for a more chaotic location and crowd. After stocking up on a sufficient number of Barbie accessories (Ava was in a girly phase at the time), we [&#8230;]</p>
  425. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/03/17/saint-patricks-day-remember/">A Saint Patrick’s Day to remember</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  426. ]]></description>
  427. <content:encoded><![CDATA[<img src="http://www.zeldman.com/wp-content/themes/zeldman/images/default.svg" class="lede" alt="" /><p>WHEN my daughter Ava was much younger—about seven—I took her to Toys R Us in Times Square one Saturday that was also Saint Patrick’s Day. You couldn’t ask for a more chaotic location and crowd. After stocking up on a sufficient number of Barbie accessories (Ava was in a girly phase at the time), we headed out of the store and toward home. </p>
  428. <p>It was a hot March that year. Unseasonably sweltering. The streets were unwalkable—thickly thronged with drunks and tourists—and there were no cabs to be seen. So we ended up hiring a bike rickshaw to take us home. I’d recently done the same thing in Austin, where the ride cost $10. The sign on the New York rickshaw also said $10. Unfortunately, it meant $10 per city block—as I discovered to my cost, and horror, upon trying to exit when we finally reached our destination.</p>
  429. <p>But the ludicrous overcharge was worth it, because the trip created a memory.</p>
  430. <p>Ava is half Irish Catholic and Bohemian on her mother’s side, half Ukranian and Russian Jewish on my side. At the time, she identified Irishness with her mother’s qualities, such as intelligence, warmth, and elegance. She did not know that Saint Patrick’s Day in major U.S. cities is mainly an excuse for high school and college students from out of town to come fall down drunk in the street.</p>
  431. <p>As our rickshaw driver pedaled his way to the bank, we passed wave after wave of staggering, shouting, woohooing greenclad coeds, accompanied by slightly less inebriated predator dates. The women shrilled “hey” at us. They stumbled into the crosswalk. They vomited between parked cars and then made out with their companions.</p>
  432. <p>Hammering down 38th Street in the shuddering rickshaw, Ava got up on her hind legs. “You’re a disgrace to the Irish!” she shouted.</p>
  433. <p>A drunken collegiate, making eye contact with the child while not necessarily understanding her words, shouted, &#8220;Woo-hoo!&#8221; and belched.</p>
  434. <p>I think of it every Saint Patrick&#8217;s Day in New York. The righteously indignant little girl, the sweating Asian immigrant bicyclist, and the sea of drunken adolescents out of Trenton and Staten.</p>
  435. <p>Mainly I think whimsically of those words. “You’re a disgrace to the Irish!” </p>
  436. <p>The post <a rel="nofollow" href="http://www.zeldman.com/2017/03/17/saint-patricks-day-remember/">A Saint Patrick’s Day to remember</a> appeared first on <a rel="nofollow" href="http://www.zeldman.com">Zeldman on Web &amp; Interaction Design</a>.</p>
  437. ]]></content:encoded>
  438. <post-id xmlns="com-wordpress:feed-additions:1">14506</post-id> </item>
  439. </channel>
  440. </rss>
  441.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.zeldman.com/rss/

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda