<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Static Sites on API Coding</title>
    <link>https://apicoding.com/tags/static-sites/</link>
    <description>Recent content in Static Sites on API Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 21 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicoding.com/tags/static-sites/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Caching a Third-Party API Response in a Cloudflare Pages Function</title>
      <link>https://apicoding.com/caching-a-third-party-api-response-in-a-cloudflare-pages-function/</link>
      <pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://apicoding.com/caching-a-third-party-api-response-in-a-cloudflare-pages-function/</guid>
      <description>&lt;p&gt;Build-time fetching handles most third-party data on a static site. It falls down in one specific case: content that should change on a schedule you are not rebuilding on. A page showing twelve rotating items each day, with a weekly deploy cadence, cannot get its data from the build.&lt;/p&gt;&#xA;&lt;p&gt;The naive fix puts a &lt;code&gt;fetch&lt;/code&gt; in the browser. Every visitor then hits the upstream API directly, which burns through rate limits, exposes any key you are using, and leaves the page empty when the provider has a bad afternoon.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
