<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hugo on Robert Terakedis</title>
    <link>https://blog.terakedis.dev/tags/hugo/</link>
    <description>Recent content in Hugo on Robert Terakedis</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Copyright © 2020 Robert Terakedis; all rights reserved.</copyright>
    <lastBuildDate>Sat, 21 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.terakedis.dev/tags/hugo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to host blog images for free with Backblaze B2 and Cloudflare</title>
      <link>https://blog.terakedis.dev/post/b2-cloudflare-image-hosting/</link>
      <pubDate>Sat, 21 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/b2-cloudflare-image-hosting/</guid>
      <description>
        
          
            &lt;p&gt;When I migrated this blog to Hugo, I had to figure out where images would live. My original thought was simple enough: store them in the GitHub repo. That worked fine for six months. Then I started thinking about what happens when I have hundreds of posts with images, and the repo turns into a photo dump.&lt;/p&gt;
&lt;p&gt;I looked at Cloudflare Images next. It seemed obvious—I&#39;m already paying for Cloudflare for DNS and SSL. But the pricing pushed me away: the transform API costs add up if you&#39;re generating variants (WebP, different sizes), and I&#39;d be locking myself into Cloudflare&#39;s image manipulation if I ever wanted to migrate. That didn&#39;t feel like room to grow.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Ensuring Domain Name Survival</title>
      <link>https://blog.terakedis.dev/post/ensuring-domain-name-survival/</link>
      <pubDate>Fri, 24 Jun 2022 21:54:25 -0400</pubDate>
      
      <guid>https://blog.terakedis.dev/post/ensuring-domain-name-survival/</guid>
      <description>
        
          
            &lt;p&gt;I was listening to the &lt;a href=&#34;https://twit.tv/posts/transcripts/security-now-episode-885-transcript&#34;&gt;Security Now Podcast&lt;/a&gt; the other day, and a GREAT topic came up that I wanted to write about.  That topic, as covered by Leo and Steve, involves ownership (specifically registrants) of Domain Name System (DNS) records.  I know from past experience, domain &amp;quot;ownership&amp;quot; never seems to be front-of-mind for many folks deciding to start a website.  Whether you&#39;re simply looking to blog, or starting a new business, the focus tends to be on the outcome (&amp;quot;I have a new website&amp;quot;) than the path to get there.   In this article, I want to cover some of the common ways domains are registered and how you can protect your domain name should something ever happen.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Change From Beautifulhugo to Clarity Theme</title>
      <link>https://blog.terakedis.dev/post/change-from-beautifulhugo-to-clarity-theme/</link>
      <pubDate>Fri, 11 Feb 2022 12:24:02 -0500</pubDate>
      
      <guid>https://blog.terakedis.dev/post/change-from-beautifulhugo-to-clarity-theme/</guid>
      <description>
        
          
            &lt;p&gt;Since I first started this blog, I was using a theme called &lt;a href=&#34;https://github.com/halogenica/beautifulhugo&#34;&gt;BeautifulHugo&lt;/a&gt;.  The theme was great and for the most part visually appealing.  However, there were some changes I was hoping to see made to the theme that never really manifested.   I had even contributed back some of my own changes, but it appeared the theme had been abandoned by it&#39;s creator.  I set about looking for a new theme and stumbled onto &lt;a href=&#34;https://github.com/chipzoller/hugo-clarity&#34;&gt;hugo-clarity&lt;/a&gt;.  Not only was this theme visually appealing to me, but I could see regular changes being made to the theme.  Yes, a theme still under active maintenance!&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>