<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog · Danylo Morhun</title>
    <link>https://www.danylomorhun.com/blog</link>
    <description>Notes from building web products: bugs worth explaining, architecture decisions, and what I learned shipping them.</description>
    <language>en-US</language>
    <atom:link href="https://www.danylomorhun.com/blog/rss.xml" rel="self" type="application/rss+xml"/>
    <lastBuildDate>Mon, 16 Nov 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>Matching the browser&apos;s color to a theme the server can&apos;t see</title>
      <link>https://www.danylomorhun.com/blog/theme-color-before-hydration</link>
      <guid isPermaLink="true">https://www.danylomorhun.com/blog/theme-color-before-hydration</guid>
      <description>A dark site with a light browser bar looks broken. Here&apos;s how to set theme-color for a light/dark site when the server doesn&apos;t know which theme the reader picked.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
      <category>nuxt</category>
      <category>css</category>
      <category>dark mode</category>
    </item>
    <item>
      <title>When the WebGL context never comes back</title>
      <link>https://www.danylomorhun.com/blog/webgl-context-lost-for-good</link>
      <guid isPermaLink="true">https://www.danylomorhun.com/blog/webgl-context-lost-for-good</guid>
      <description>My site&apos;s three.js hero sometimes went blank and stayed blank. The cause was a lost WebGL context the browser never restored. Here&apos;s how to detect it, rebuild the renderer, and test it in CI.</description>
      <pubDate>Sat, 07 Nov 2026 00:00:00 GMT</pubDate>
      <category>three.js</category>
      <category>webgl</category>
      <category>debugging</category>
    </item>
  </channel>
</rss>
