<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Automation on Ajay Dhungel</title>
    <link>/tags/automation/</link>
    <description>Recent content in Automation on Ajay Dhungel</description>
    <generator>Hugo 0.125.0</generator>
    <language>en</language>
    <copyright>DevOps Engineer | Cloud Infrastructure | AWS</copyright>
    <lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/automation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>I Built a Portfolio Site That Updates Itself Every Night</title>
      <link>/posts/automated-portfolio/</link>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <guid>/posts/automated-portfolio/</guid>
      <description>The Problem with Portfolio Sites I had let mine go stale for months. I&amp;rsquo;d shipped projects, written posts, earned certifications, and none of it showed up because updating the site meant carving out time I never had. At some point I stopped pretending discipline was the answer and just automated the whole thing.&#xA;This post covers how I wired four external data sources into a Hugo site that updates itself nightly, with a CI/CD pipeline that tests, builds, and deploys without me touching anything.</description>
    </item>
  </channel>
</rss>
