<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Design on RenderCache.com</title>
    <link>https://rendercache.com/tags/design/</link>
    <description>Recent content in Design on RenderCache.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 16 Oct 2026 18:00:00 +0300</lastBuildDate>
    <atom:link href="https://rendercache.com/tags/design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Warm before the crawler arrives</title>
      <link>https://rendercache.com/warm-before-the-crawler/</link>
      <pubDate>Fri, 16 Oct 2026 18:00:00 +0300</pubDate>
      <guid>https://rendercache.com/warm-before-the-crawler/</guid>
      <description>&lt;p&gt;The difficult request is the first one. If a crawler reaches a JavaScript page before a snapshot exists, starting Chrome at that moment adds work to an already waiting client. RenderCache&amp;rsquo;s alpha takes a different starting point: discover the public URLs from the sitemap, then render them before requests need the saved HTML.&lt;/p&gt;&#xA;&lt;p&gt;The worker queue is bounded. Missing pages get priority, refreshes are scheduled, and repeated work for a page is deduplicated. That does not make coverage automatic: an empty sitemap, a failed browser or a wrong readiness selector can leave pages without useful snapshots. The status page therefore shows what is discovered, cached, missing, queued and failing, with request-added pages reported separately.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
