
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, and data engineering — plus mindset essays on confidence, routines, health, and sport psychology.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Sun, 09 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/ui-design/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-09-ten-gui-elements-alphabet.en</guid>
    <title>A Screen Is Written With Ten Letters — The One Question to Ask Before Building a Custom Widget</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-09-ten-gui-elements-alphabet.en</link>
    <description>Jakob Nielsen has laid out the claim that almost every user interface is assembled from about ten elements, the way every English word is written with twenty-six letters. The list is useful not because it tells you what to build but because it shows what you actually throw away when you build a new widget. This post covers the information carried by the ranking, four common ways a team half-breaks a convention, and a labelling exercise you can run on your own design system inventory today.</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ui-design</category><category>ux</category><category>design-system</category><category>frontend</category><category>usability</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-09-ten-gui-elements-alphabet.ja</guid>
    <title>画面は十文字で書かれます — カスタムウィジェットを作る前に問うべきひとつのこと</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-09-ten-gui-elements-alphabet.ja</link>
    <description>ヤコブ・ニールセンは、ほぼすべてのユーザーインターフェースが十個ほどの要素で組み立てられると整理しました。アルファベット二十六文字ですべての英単語を書くのと同じように、です。この一覧が有用なのは何を作るべきかを教えるからではなく、新しいウィジェットを作るとき実際には何を捨てているのかを見せてくれるからです。順位が含んでいる情報、慣習を半分だけ破ってしまう四つのよくあるやり方、そして自分たちのデザインシステム一覧に今日つけられるラベルまで整理しました。</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ui-design</category><category>ux</category><category>design-system</category><category>frontend</category><category>usability</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-09-ten-gui-elements-alphabet</guid>
    <title>화면은 열 글자로 쓰입니다 — 커스텀 위젯을 만들기 전에 물어야 할 한 가지</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-09-ten-gui-elements-alphabet</link>
    <description>제이콥 닐슨은 거의 모든 사용자 인터페이스가 열 개 남짓한 요소로 조립된다고 정리했습니다. 알파벳 스물여섯 글자로 모든 영어 단어를 쓰듯이 말입니다. 이 목록이 유용한 이유는 무엇을 만들지 알려 주기 때문이 아니라, 새 위젯을 만들 때 실제로 무엇을 버리는지 보여 주기 때문입니다. 순위가 담고 있는 정보, 관습을 어기는 네 가지 흔한 방식, 그리고 우리 디자인 시스템 목록에 오늘 붙여 볼 수 있는 라벨까지 정리했습니다.</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ui-design</category><category>ux</category><category>design-system</category><category>frontend</category><category>usability</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-09-ten-gui-elements-alphabet.zh</guid>
    <title>界面是用十个字母写成的 —— 做自定义控件之前必须问的一个问题</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-09-ten-gui-elements-alphabet.zh</link>
    <description>雅各布·尼尔森整理出一个说法：几乎所有用户界面都是由十来个元素拼起来的，就像二十六个字母能写出所有英文单词一样。这份清单之所以有用，不是因为它告诉你该做什么，而是因为它让你看清做一个新控件时实际上丢掉了什么。本文梳理排名本身携带的信息、把约定破坏一半的四种常见做法，以及今天就能贴到自家设计系统清单上的标签。</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>ui-design</category><category>ux</category><category>design-system</category><category>frontend</category><category>usability</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-09-web-editors-have-no-page-model.en</guid>
    <title>The Real Reason Web Editors Have No Ruler — The Ruler Is Not Missing, the Paper Is</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-09-web-editors-have-no-page-model.en</link>
    <description>Of everything Word has and web editors do not, the most frequently requested feature is the ruler. It is not that nobody has built one. It is that the web has no page model, so you cannot even settle what a centimetre is a centimetre of. Taking the recently published editor-ruler as a thread to pull, this post lays out why attaching a ruler is a decision to bring in a document model rather than a UI part, and what follows from that decision.</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>frontend</category><category>rich-text-editor</category><category>ui-design</category><category>contenteditable</category><category>developer-tools</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-09-web-editors-have-no-page-model.ja</guid>
    <title>ウェブエディタに定規が無い本当の理由 — 測る定規が無いのではなく、測る紙が無いのです</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-09-web-editors-have-no-page-model.ja</link>
    <description>Wordにあってウェブエディタに無いもののうち、もっともよく要望される機能がルーラーです。誰も作っていないからではありません。ウェブにはページというモデルが無いので、センチメートルが何に対するセンチメートルなのかから決められないからです。最近公開されたeditor-rulerを手がかりに、ルーラーをつけるという決定がなぜUI部品ひとつではなく文書モデルひとつを引き入れる決定なのか、そしてその決定に何がついてくるのかを整理しました。</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>frontend</category><category>rich-text-editor</category><category>ui-design</category><category>contenteditable</category><category>developer-tools</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-09-web-editors-have-no-page-model</guid>
    <title>웹 에디터에 자가 없는 진짜 이유 — 잴 자가 없는 게 아니라 잴 종이가 없습니다</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-09-web-editors-have-no-page-model</link>
    <description>워드에는 있고 웹 에디터에는 없는 것 중 가장 자주 요청받는 기능이 눈금자입니다. 아무도 만들지 않아서가 아닙니다. 웹에는 페이지라는 모델이 없어서 센티미터가 무엇에 대한 센티미터인지부터 정할 수 없기 때문입니다. 최근 공개된 editor-ruler를 실마리 삼아, 눈금자를 붙인다는 결정이 왜 UI 부품 하나가 아니라 문서 모델 하나를 들이는 결정인지, 그리고 그 결정에 따라오는 것이 무엇인지 정리했습니다.</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>frontend</category><category>rich-text-editor</category><category>ui-design</category><category>contenteditable</category><category>developer-tools</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-09-web-editors-have-no-page-model.zh</guid>
    <title>Web 编辑器没有标尺的真正原因 —— 缺的不是尺，是纸</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-09-web-editors-have-no-page-model.zh</link>
    <description>Word 有而 Web 编辑器没有的功能里，被要求得最频繁的就是标尺。这不是因为没人做，而是因为 Web 里没有「页」这个模型，连「厘米是相对于什么的厘米」都定不下来。本文以最近公开的 editor-ruler 为线索，梳理为什么「加一把标尺」这个决定不是加一个 UI 部件，而是引入一整套文档模型，以及这个决定会牵出什么。</description>
    <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>frontend</category><category>rich-text-editor</category><category>ui-design</category><category>contenteditable</category><category>developer-tools</category>
  </item>

    </channel>
  </rss>
