<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Build Time on API Coding</title>
    <link>https://apicoding.com/tags/build-time/</link>
    <description>Recent content in Build Time 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/build-time/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fetching a Remote JSON API at Build Time in Hugo with resources.GetRemote</title>
      <link>https://apicoding.com/fetching-a-remote-json-api-at-build-time-in-hugo-with-resources.getremote/</link>
      <pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://apicoding.com/fetching-a-remote-json-api-at-build-time-in-hugo-with-resources.getremote/</guid>
      <description>&lt;p&gt;Most tutorials that put third-party API data on a static site reach for client-side JavaScript. The page loads, a &lt;code&gt;fetch&lt;/code&gt; runs, and content appears a moment later. It works, and it throws away most of what a static site is for. Search engines see an empty container, every visitor costs you an upstream request, and a rate limit or an outage at the provider becomes a broken page for everyone.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
