<?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 Junian Dev</title>
    <link>https://www.junian.dev/tags/hugo/</link>
    <description>Recent content in Hugo on Junian Dev</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>author@junian.dev (Junian Triajianto)</managingEditor>
    <webMaster>author@junian.dev (Junian Triajianto)</webMaster>
    <copyright>Copyright &amp;copy; 2014 - 2026 Junian.dev</copyright>
    
	    <atom:link href="https://www.junian.dev/tags/hugo/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Google Adsense Domain Migration: The Planning</title>
      <link>https://www.junian.dev/blog/google-adsense-domain-migration/</link>
      <pubDate>Fri, 20 Feb 2026 04:00:00 +0700</pubDate>
      <author>author@junian.dev (Junian Triajianto)</author>
      <guid>https://www.junian.dev/blog/google-adsense-domain-migration/</guid>
      <description>&lt;p&gt;Lately, my website has been gaining great traffic, and I’m truly grateful for that, especially you: human readers.&lt;/p&gt;
&lt;p&gt;It makes me happy to keep writing more content.
The fact that people are actually reading what I write is something I never expected, especially in this age of AI.&lt;/p&gt;
&lt;p&gt;There’s also another thing I’ve been planning to do.&lt;/p&gt;
&lt;p&gt;I’ve been meaning to buy a &lt;code&gt;.com&lt;/code&gt; domain for rebranding, and I thought this might be a good time to do it before someone else snatches it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Set the Default Hugo Archetypes to the Next Day</title>
      <link>https://www.junian.dev/dev/hugo-archetypes-default-date-next-day/</link>
      <pubDate>Mon, 02 Feb 2026 19:00:00 +0700</pubDate>
      <author>author@junian.dev (Junian Triajianto)</author>
      <guid>https://www.junian.dev/dev/hugo-archetypes-default-date-next-day/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;re using the Hugo static site generator, the default date and time assigned to new content is the current date and time.
That’s perfectly normal, but what if you want to set the date to a different day, such as tomorrow or any other future date?&lt;/p&gt;
&lt;p&gt;I often need this because I usually write drafts today and publish them the next day.&lt;/p&gt;
&lt;p&gt;By default, the &lt;code&gt;date&lt;/code&gt; and &lt;code&gt;publishDate&lt;/code&gt; fields are typically defined in the &lt;code&gt;archetypes/default.md&lt;/code&gt; file like this:&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Fix Hugo JSON-LD Escaping Problem</title>
      <link>https://www.junian.dev/dev/hugo-fix-json-ld-escaping/</link>
      <pubDate>Thu, 02 Apr 2020 21:35:54 +0700</pubDate>
      <author>author@junian.dev (Junian Triajianto)</author>
      <guid>https://www.junian.dev/dev/hugo-fix-json-ld-escaping/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve been using Hugo static site generator for a long time.
It&amp;rsquo;s from version 0.34 if I remember correctly.
I&amp;rsquo;ve been using that version for a year and so far it works just fine.
I build my theme based on that version too.
And it&amp;rsquo;s been forever I keep the theme code as it is because I thought that&amp;rsquo;s good enough.&lt;/p&gt;
&lt;p&gt;Recently I decided to give the update for Hugo version 0.68.3.
The purpose is just to want to catch up with the latest version.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Full-Text RSS in Hugo</title>
      <link>https://www.junian.dev/dev/hugo-full-text-rss/</link>
      <pubDate>Tue, 26 Feb 2019 13:15:56 +0700</pubDate>
      <author>author@junian.dev (Junian Triajianto)</author>
      <guid>https://www.junian.dev/dev/hugo-full-text-rss/</guid>
      <description>How to include full blog content in Hugo-generated site&#39;s RSS</description>
    </item>
    <item>
      <title>Inserting an Ad Unit to Hugo Content without Shortcode</title>
      <link>https://www.junian.dev/dev/hugo-in-article-ad/</link>
      <pubDate>Thu, 09 Aug 2018 09:12:59 +0700</pubDate>
      <author>author@junian.dev (Junian Triajianto)</author>
      <guid>https://www.junian.dev/dev/hugo-in-article-ad/</guid>
      <description>&lt;p&gt;Recently I just discovered that Google AdSense now have a &lt;a href=&#34;https://support.google.com/adsense/answer/7320111?hl=en&#34;&gt;native in-article ad unit&lt;/a&gt;.
This is interesting because this ad unit blend well with the content but reader will still easily tell if it&amp;rsquo;s an ad.
Since Google already optimize it, we as publisher won&amp;rsquo;t need to worry too much about intrusive ads in the middle of article.&lt;/p&gt;
&lt;p&gt;So now I want to try put it in my Hugo static site.
You can actually use hugo shortcode for this, there is nothing wrong with that.
But writing a simple html tag is easier than writing a shortcode in the middle of article.
Not to mention, your markdown file will still valid based on CommonMark spec.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Wrap Image with Figure Tag on Hugo without Shortcode</title>
      <link>https://www.junian.dev/dev/hugo-image-figure-wrap/</link>
      <pubDate>Sun, 05 Aug 2018 00:13:16 +0700</pubDate>
      <author>author@junian.dev (Junian Triajianto)</author>
      <guid>https://www.junian.dev/dev/hugo-image-figure-wrap/</guid>
      <description>&lt;p&gt;Recently I&amp;rsquo;ve been thinking of migrating my blog from Blogger.com to a static site.
After doing some research I decided to use Hugo.&lt;/p&gt;
&lt;p&gt;One thing I like about Hugo is that they can produce a site from Markdown files.
Now this markdown file is following CommonMark spec by default, which is great.
But I have a case to always wrap images of my content inside a &lt;code&gt;figure&lt;/code&gt; tag.&lt;/p&gt;
&lt;p&gt;I actually can do this using Hugo &lt;a href=&#34;https://gohugo.io/content-management/shortcodes/#figure&#34;&gt;shortcode&lt;/a&gt;, but I don&amp;rsquo;t want to use that because I want to make sure my markdown files follow CommonMark spec. So it must be pure Markdown content with frontmatter, without filling it with a custom rule from Hugo.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
