<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cicd :: Tag :: Full Stack DevOps The Architect’s Log</title>
    <link>http://localhost:1313/tags/cicd/index.html</link>
    <description></description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 02 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://localhost:1313/tags/cicd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Day 1: The Static Foundation - Automating Hugo Like a Pro</title>
      <link>http://localhost:1313/100-days/001-hugo/index.html</link>
      <pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/100-days/001-hugo/index.html</guid>
      <description>The first step in the 100-day DevOps and Solution Architecture journey, is choosing a platform that is as fast and pragmatic as the systems I build.&#xA;I’ve been coding for 20 years so I’ve seen the web cycle through endless bloat HTML 3, HTML 4, Flash, and now JavaScript bloat. For this project, I’m returning to the most efficient stack possible. Static sites with Hugo.&#xA;Why Hugo? Hugo is a static site generator written in Go. It’s a single binary you can copy and paste around. THis means no need for any dependencies, no npm install hell, no broken dependencies, and zero maintenance. Plug and play ready. It’s perfect for documentation, blogs, and even commercial sites that need to be lightning fast. If you deploy a site with Hugo it’s going to be almost 100% secure (unless you manage to somehow add a NPM cryptobot to your local environment :facepalm:)</description>
    </item>
  </channel>
</rss>