A place to cache linked articles (think custom and personal wayback machine)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

index.html 7.0KB

4 years ago
  1. <!doctype html><!-- This is a valid HTML5 document. -->
  2. <!-- Screen readers, SEO, extensions and so on. -->
  3. <html lang="fr">
  4. <!-- Has to be within the first 1024 bytes, hence before the <title>
  5. See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
  6. <meta charset="utf-8">
  7. <!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
  8. <!-- The viewport meta is quite crowded and we are responsible for that.
  9. See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
  10. <meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1,shrink-to-fit=no">
  11. <!-- Required to make a valid HTML5 document. -->
  12. <title>Redesign: Wants and Needs (archive) — David Larlet</title>
  13. <!-- Lightest blank gif, avoids an extra query to the server. -->
  14. <link rel="icon" href="data:;base64,iVBORw0KGgo=">
  15. <!-- Thank you Florens! -->
  16. <link rel="stylesheet" href="/static/david/css/style_2020-01-09.css">
  17. <!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
  18. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" crossorigin>
  19. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" crossorigin>
  20. <link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" crossorigin>
  21. <meta name="robots" content="noindex, nofollow">
  22. <meta content="origin-when-cross-origin" name="referrer">
  23. <!-- Canonical URL for SEO purposes -->
  24. <link rel="canonical" href="https://frankchimero.com/blog/2020/wants-and-needs/">
  25. <body class="remarkdown h1-underline h2-underline hr-center ul-star pre-tick">
  26. <article>
  27. <h1>Redesign: Wants and Needs</h1>
  28. <h2><a href="https://frankchimero.com/blog/2020/wants-and-needs/">Source originale du contenu</a></h2>
  29. <p>Let’s oversimplify for a bit to help get down some goals for the site redesign.</p>
  30. <h3 id="the-website-spectrum">The website spectrum</h3>
  31. <p>Websites sit on a design spectrum. On one end are applications, with their conditional logic, states, and flows—they’re software. The design challenge here is to create designs that support everything the product could contain and become. Google Maps in the browser is probably the most purely appy application I can imagine, but any design system supporting variable content and conditional states is going to be pretty appy and have exponential complexity.</p>
  32. <p>Large systems, unknowableness, and unseeableness come together in the same carriage. When this joins up with a designer’s natural desire for control and comprehensiveness, it creates fertile ground for unwarranted impostor syndrome—playing the right game by the wrong rules. (If this line of thinking is interesting to you, give Robin Rendle’s <a href="https://www.robinrendle.com/essays/systems-mistakes-and-the-sea">Systems, Mistakes, and the Sea</a> a read.) More on this in a bit.</p>
  33. <p>On the other end of the design spectrum are documents; sweet, modest documents with their pleasing knowableness and clear edges. They only need to achieve readability with hierarchy and layout—they’re writing and records. The design challenge is to make it look like what it is, because the content is all there in front of you. If you’re looking for a purely documenty document website, I’d nominate blog-based personal websites as the platonic example.</p>
  34. <h3 id="hiding-in-docs">Hiding in docs</h3>
  35. <p>I love personal sites because you can get your head around what you’re doing. Their design challenges are primarily typographic—what are the typefaces, how do we use them to express hierarchy, how is the text block set to support reading, where do those text blocks go on the page, and how does that layout change across viewports? These challenges exist in the design of apps, but the approach is haunted by hidden complexity. When designing a document, you can check and see how your choices hold up. It’s 1:1, without much need to project decisions out into the fog of complexity.</p>
  36. <p>I’ve redesigned my site a lot in the last decade. A <em>lot</em>. Too much and too frequently, most certainly. The stated reason was to practice using new methods (trying CSS grid, taking a new typeface for a spin, and so on). But that isn’t the full story. Too often, I’d redesign because I needed to feel capable at my job, which required a design challenge that wouldn’t drive me nuts. The simplicity of redesigning my personal site became a way to hide from the crazy-making and humbling (humiliating?) complexity of systems design. The redesigns were a happy little bubble of sensibility and control, a way to practice and use technology at work without feeling trapped.</p>
  37. <p>For better or worse, I am a document lover. All of my best intentions to try new digital tools eventually devolve to their most stable ur-forms of text files and spreadsheets. I think back to what hooked me on the web in 1996—our expectations are so often defined by our first loves. The primitive parts of me will always want websites to be editable documents with legible, marked up text on servers. I began making websites when mastery seemed so possible that people called themselves “webmasters.” Those expectations are laughable now.</p>
  38. <p>This is the context where I fell in love with design and the web. It is a love story, but it is also a ghost story.</p>
  39. <h3 id="carving-out-a-space">Carving out a space</h3>
  40. <p>Still, personal websites are personal before they are anything else. You can carve out a space in whatever shape you’d like, even one of a ghost. I anticipate this personal site redesign to follow a path back to basics. Here is where I’d like to end up:</p>
  41. <ul>
  42. <li><strong>Good fit</strong>: Make it look like what it is—a place to write and keep records. A collection of documents. Website as filing cabinet.</li>
  43. <li><strong>Modest elegance</strong>: Think elevated defaultness. Premium vanilla ice cream, top shelf ingredients used modestly and well. Tight focus on typography for better reading and suggestion of craft and quality. No tacky razzle-dazzle.</li>
  44. <li><strong>Feeling of lightness</strong>: Simple design, clear patterns, shallow hierarchy. As little javascript as possible, preferably none. Clear markup, no junk. The inside of the site looks like the outside.</li>
  45. <li><strong>Whim</strong>: Achieve all of the above without being austere or over-serious. Have some fun. Smile a bit. No black turtleneck design.</li>
  46. </ul>
  47. </article>
  48. <hr>
  49. <footer>
  50. <p>
  51. <a href="/david/" title="Aller à l’accueil">🏠</a> •
  52. <a href="/david/log/" title="Accès au flux RSS">🤖</a> •
  53. <a href="http://larlet.com" title="Go to my English profile" data-instant>🇨🇦</a> •
  54. <a href="mailto:david%40larlet.fr" title="Envoyer un courriel">📮</a> •
  55. <abbr title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340">🧚</abbr>
  56. </p>
  57. </footer>
  58. <script src="/static/david/js/instantpage-3.0.0.min.js" type="module" defer></script>
  59. </body>
  60. </html>