https://yanqian.github.io/series/obsidian-publishing-pipeline/Recent content in Obsidian Publishing Pipeline on Armstrong YanHugoen-USWed, 22 Jul 2026 00:18:29 +0800https://yanqian.github.io/posts/publish/building-a-human-gated-bilingual-publishing-pipeline-with-obsidian-and-hugo/Wed, 22 Jul 2026 00:18:29 +0800https://yanqian.github.io/posts/publish/building-a-human-gated-bilingual-publishing-pipeline-with-obsidian-and-hugo/<p>In <a href="https://yanqian.github.io/posts/publish/building-a-personal-blog-with-obsidian-hugo-and-github-pages/" class="external-link" target="_blank" rel="noopener">Building a Private-to-Public Publishing Pipeline with Obsidian, Hugo, and GitHub Pages</a>, I described the boundary that keeps my private vault separate from my public website.</p> <p>That solved where an article should live. It did not solve what happens when the same article needs to exist in two languages.</p> <p>At first, bilingual publishing looked like a translation task: send the Markdown to a model, ask for Chinese or English, and save the response beside the original. In practice, that was the least interesting part of the problem.</p>https://yanqian.github.io/posts/publish/building-a-personal-blog-with-obsidian-hugo-and-github-pages/Tue, 21 Jul 2026 09:11:29 +0800https://yanqian.github.io/posts/publish/building-a-personal-blog-with-obsidian-hugo-and-github-pages/<p>I recently rebuilt my personal website around a simple idea:</p> <p>Keep Obsidian as the private source of truth, and selectively publish public notes into a clean personal website.</p> <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.</p> <p>This article documents the architecture, tradeoffs, and workflow I ended up with.</p> <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.</p>