<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Github-Pages on Dyn</title><link>https://cmduyeen.github.io/tags/github-pages/</link><description>Recent content in Github-Pages on Dyn</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 16 Oct 2026 20:30:00 +0700</lastBuildDate><atom:link href="https://cmduyeen.github.io/tags/github-pages/index.xml" rel="self" type="application/rss+xml"/><item><title>From Obsidian to GitHub Pages, Part 3: Test RSS and Profile Sync</title><link>https://cmduyeen.github.io/posts/obsidian-to-github-blog-03-test-rss-and-profile-sync/</link><pubDate>Fri, 16 Oct 2026 20:30:00 +0700</pubDate><guid>https://cmduyeen.github.io/posts/obsidian-to-github-blog-03-test-rss-and-profile-sync/</guid><description>&lt;p>We&amp;rsquo;ve written a post in Obsidian and pushed it through Hugo to GitHub Pages. This final part verifies the two public outputs that make the workflow useful: the blog&amp;rsquo;s RSS feed and the blog-post list in the GitHub profile README.&lt;/p>
&lt;h2 id="check-the-deployed-article-and-feed">Check the deployed article and feed&lt;/h2>
&lt;p>After pushing to &lt;code>main&lt;/code>, open the &lt;strong>Build and deploy blog&lt;/strong> workflow in the blog repository. Wait for both the build and deploy jobs to finish successfully, then visit the site&amp;rsquo;s home page and open the article.&lt;/p></description><image>https://cmduyeen.github.io/images/posts/rss-profile-sync.svg</image></item><item><title>From Obsidian to GitHub Pages, Part 2: Publish Markdown with Hugo</title><link>https://cmduyeen.github.io/posts/obsidian-to-github-blog-02-publish-with-hugo/</link><pubDate>Thu, 15 Oct 2026 09:00:00 +0700</pubDate><guid>https://cmduyeen.github.io/posts/obsidian-to-github-blog-02-publish-with-hugo/</guid><description>&lt;p>In &lt;a href="https://cmduyeen.github.io/posts/obsidian-to-github-blog-01-publishable-vault/">Part 1&lt;/a>, we set up Obsidian to edit the blog&amp;rsquo;s Markdown source. Now we&amp;rsquo;ll publish a post and see how it reaches the live site.&lt;/p>
&lt;h2 id="save-the-note-in-hugos-content-folder">Save the note in Hugo&amp;rsquo;s content folder&lt;/h2>
&lt;p>Create or edit a &lt;code>.md&lt;/code> file in &lt;code>content/posts/&lt;/code>. A published article needs front matter with a title, date, &lt;code>draft: false&lt;/code>, and any useful tags:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-yaml" data-lang="yaml">&lt;span style="display:flex;">&lt;span>---
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">title&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;My first Obsidian post&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">date&lt;/span>: &lt;span style="color:#e6db74">2026-10-16T21:00:00&lt;/span>&lt;span style="color:#ae81ff">+07&lt;/span>:&lt;span style="color:#ae81ff">00&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">draft&lt;/span>: &lt;span style="color:#66d9ef">false&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#f92672">tags&lt;/span>: [&lt;span style="color:#e6db74">&amp;#34;obsidian&amp;#34;&lt;/span>, &lt;span style="color:#e6db74">&amp;#34;first-post&amp;#34;&lt;/span>]
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>---
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Write the article below the front matter using standard Markdown headings, paragraphs, lists, code fences, and links. A preview in Obsidian checks the Markdown formatting, but it does not fully reproduce the PaperMod theme; check the deployed page after publishing too.&lt;/p></description><image>https://cmduyeen.github.io/images/posts/hugo-publishing.svg</image></item></channel></rss>