<?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 Armstrong Yan</title><link>https://yanqian.github.io/topics/hugo/</link><description>Recent content in Hugo on Armstrong Yan</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 08 May 2026 22:48:50 +0800</lastBuildDate><atom:link href="https://yanqian.github.io/topics/hugo/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Private-to-Public Publishing Pipeline with Obsidian, Hugo, and GitHub Pages</title><link>https://yanqian.github.io/posts/publish/building-a-personal-blog-with-obsidian-hugo-and-github-pages/</link><pubDate>Fri, 08 May 2026 22:48:50 +0800</pubDate><guid>https://yanqian.github.io/posts/publish/building-a-personal-blog-with-obsidian-hugo-and-github-pages/</guid><description>&lt;p>I recently rebuilt my personal website around a simple idea:&lt;/p>
&lt;p>Keep Obsidian as the private source of truth, and selectively publish public notes into a clean personal website.&lt;/p>
&lt;p>This is less a Hugo tutorial and more a note about designing a publishing boundary between a private knowledge base and a public website.&lt;/p>
&lt;p>This article documents the architecture, tradeoffs, and workflow I ended up with.&lt;/p>
&lt;p>The repository names, URLs, and site pages in this article come from my own setup. If you follow the same approach, replace them with your GitHub username, repository name, domain, and navigation structure.&lt;/p></description></item></channel></rss>