<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Cloudflare-Pages on AD8FD</title>
    <link>https://ad8fd.com/tags/cloudflare-pages/</link>
    <description>Recent content in Cloudflare-Pages on AD8FD</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <managingEditor>bbathe@willyboy.com (Brian Bathe)</managingEditor>
    <webMaster>bbathe@willyboy.com (Brian Bathe)</webMaster>
    <lastBuildDate>Mon, 22 Dec 2025 11:40:15 -0500</lastBuildDate>
    <atom:link href="https://ad8fd.com/tags/cloudflare-pages/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Standing Up This Site</title>
      <link>https://ad8fd.com/posts/standing-up-this-site/</link>
      <pubDate>Mon, 22 Dec 2025 11:40:15 -0500</pubDate><author>bbathe@willyboy.com (Brian Bathe)</author>
      <guid>https://ad8fd.com/posts/standing-up-this-site/</guid>
      <description>How I’m hosting my amateur radio stories using a static site stack instead of a generic blog platform.</description>
      <content:encoded><![CDATA[<p>I wanted a home for my amateur radio stories that was fast, mostly text with a few pics, version-controlled like code, and cheap to keep running.</p>
<p>So I skipped WordPress. The stack is:</p>
<ul>
<li><strong>Hugo</strong> as the static site generator</li>
<li><strong>PaperMod</strong> as the theme</li>
<li><strong>Cloudflare Pages</strong> for hosting</li>
<li><strong>Git</strong> as the publishing workflow</li>
</ul>
<p>Hugo is written in Go. Markdown and templates in, HTML out. Content is just files in a repo, builds are fast, and I can keep sections straight:</p>
<ul>
<li><code>/dxpeditions/eleuthera-2026/</code></li>
<li><code>/posts/</code></li>
<li><code>/about/</code></li>
</ul>
<p>PaperMod is a simple theme. Clean type, readable posts. I didn&rsquo;t want a heavy portfolio look or a dark terminal look.</p>
<p>Cloudflare Pages is free, it builds on push, and the workflow is <code>git commit</code>, <code>git push</code>, site updates. No database, no patching, no admin UI to babysit. Everything that matters lives in the repo.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
