<?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/categories/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>Fri, 11 Feb 2022 12:24:02 -0500</lastBuildDate><atom:link href="https://blog.terakedis.dev/categories/hugo/index.xml" rel="self" type="application/rss+xml" />
    <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>
    
    <item>
      <title>Updated GitHub Actions to Publish Hugo Site From Private to Public Repo</title>
      <link>https://blog.terakedis.dev/post/updated-github-actions-publish-private-hugo-repo-to-public-pages-site/</link>
      <pubDate>Tue, 27 Oct 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/updated-github-actions-publish-private-hugo-repo-to-public-pages-site/</guid>
      <description>
        
          
            &lt;p&gt;When I restarted my blogging journey last year, I went with Hugo to generate a static website hosted as a GitHub Pages site.  As mentioned, Blogger and WordPress always suffered recurring problems, and maintenance with WordPress still turned into a time suck due to its complexity.  By comparison, GitHub has been a nearly painless hosting provider, and the way I&#39;ve configured it has allowed me to keep drafts hidden by staging in a private repository.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Using GitHub Actions to Publish Hugo Site From Private to Public Repo</title>
      <link>https://blog.terakedis.dev/post/github-actions-publish-private-hugo-repo-to-public-pages-site/</link>
      <pubDate>Fri, 14 Aug 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/github-actions-publish-private-hugo-repo-to-public-pages-site/</guid>
      <description>
        
          
            &lt;p&gt;I restarted my blogging journey earlier this year when I started looking into &lt;del&gt;Jekyll&lt;/del&gt; Hugo to generate a static website.  I had past experience with Blogger and Wordpress, but frankly had periodic problems with both platforms that ended up being a time suck.  As it has been, Hugo has been a simplistic publishing method and GitHub a reliable (and FREE) hosting provider.  Yet, my desire to keep my drafts private (.e.g the use of 2 separate repositories) has created a small overhead in that I have to build and manually commit the website changes to the public repository to make them live.&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Another GitHub Actions Update - Using Deploy Keys Instead Of Personal Access Tokens</title>
      <link>https://blog.terakedis.dev/post/another-github-actions-update-change-hugo-publish-deploy-keys/</link>
      <pubDate>Fri, 06 Mar 2020 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/post/another-github-actions-update-change-hugo-publish-deploy-keys/</guid>
      <description>
        
          
            &lt;p&gt;When I restarted my blogging journey in 2020, I switched from Jekyll to Hugo hosted in GitHub pages.  It&#39;s been a relatively painless journey, and kudos to GitHub as a rock-solid hosting provider.  I&#39;ve covered it before (&lt;a href=&#34;https://blog.terakedis.dev/post/github-actions-publish-private-hugo-repo-to-public-pages-site/&#34;&gt;Initial Setup&lt;/a&gt; and &lt;a href=&#34;https://blog.terakedis.dev/post/updated-github-actions-publish-private-hugo-repo-to-public-pages-site/&#34;&gt;First Update&lt;/a&gt;), but I&#39;ve been incredibly happy with private-to-public publishing workflow that allows me to keep drafts and work-in-progress hidden.  That said, a recent comment gave me reason to make another update to the Workflow.   Read on for more detail...&lt;/p&gt;
          
          
        
      </description>
    </item>
    
    <item>
      <title>Welcome to Hugo (from Jekyll)</title>
      <link>https://blog.terakedis.dev/2018-06-15-welcome-to-jekyll/</link>
      <pubDate>Fri, 15 Jun 2018 00:00:00 +0000</pubDate>
      
      <guid>https://blog.terakedis.dev/2018-06-15-welcome-to-jekyll/</guid>
      <description>
        
          
            &lt;p&gt;Welcome to my wholly reworked website!  This time, I&#39;ve dropped the complexity of Wordpress and opted for something significantly simpler:  &lt;del&gt;Jekyll&lt;/del&gt; Hugo and GitHub.&lt;/p&gt;
&lt;p&gt;Having now hosted the site in GitHub Pages, here was the process I started with Hugo:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Created the Github Pages repo (rterakedis.github.io) -- this is where github pages looks for the blog&#39;s generated site files.&lt;/li&gt;
&lt;li&gt;Created a 2nd Github repo:  rterakedis.github.io.hugo -- this repo holds the source files for Hugo to parse and generate the site.&lt;/li&gt;
&lt;li&gt;Added the GH Pages repo (rterakedis.github.io) as a submodule for rterakedis.github.io.hugo&lt;/li&gt;
&lt;li&gt;Edited the config.toml in the hugo files to include the following:&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;baseURL = &amp;quot;https://terakedis.dev/&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;publishdir = &amp;quot;rterakedis.github.io&amp;quot;&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;Add the CNAME file into the rterakedis.github.io repo and enable the custom name/https in the repo settings&lt;/li&gt;
&lt;li&gt;Ensure the output from &lt;code&gt;hugo&lt;/code&gt; builds into the rterakedis.github.io directory in my local rterakedis.github.io.hugo directory&lt;/li&gt;
&lt;li&gt;Commit and push everything to GitHub&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;A few quick links that I found particularly helpful when I was working with Jekyll:&lt;/p&gt;
          
          
        
      </description>
    </item>
    
  </channel>
</rss>