<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blogging on YHY Study Website</title><link>https://ryan.0412.online/en/tags/blogging/</link><description>Recent content in Blogging on YHY Study Website</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 30 Sep 2026 21:25:01 +0800</lastBuildDate><atom:link href="https://ryan.0412.online/en/tags/blogging/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Personal Site with Oink, from Setup to Publication</title><link>https://ryan.0412.online/en/blog/oink-site-setup-notes/</link><pubDate>Sat, 29 Aug 2026 00:00:00 +0000</pubDate><guid>https://ryan.0412.online/en/blog/oink-site-setup-notes/</guid><description>&lt;p&gt;The &lt;a href="https://oink.pgsty.com/zh/book/"&gt;official Oink tutorial&lt;/a&gt; is comprehensive, but connecting the folders, configuration, and commands can still be confusing the first time, especially without much frontend experience. These notes from building &lt;a href="https://ryanyhy.github.io/YHY-Website/"&gt;YHY Study Website&lt;/a&gt; follow one path: understand Oink, learn how &lt;code&gt;content/&lt;/code&gt; is organized, and then write and publish a blog post.&lt;/p&gt;
&lt;figure class="td-figure"&gt;
 &lt;img src="https://ryan.0412.online/blog/oink-site-setup-notes/oink-site-setup-cover.png" alt="Oink site setup diagram" width="1536" height="1024" loading="lazy" decoding="async"&gt;&lt;figcaption&gt; &lt;span class="td-fig-caption"&gt;Markdown → Hugo → the Oink theme → a deployable static site&lt;/span&gt;&lt;/figcaption&gt;
&lt;/figure&gt;&lt;h2 id="stack"&gt;What Hugo and Oink each do
&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Hugo&lt;/strong&gt; is a static site generator: it reads Markdown and configuration and produces HTML.
&lt;strong&gt;Oink&lt;/strong&gt; is a Hugo theme: it controls the appearance of sidebars, cards, callouts, code blocks, and other components.&lt;/p&gt;</description></item></channel></rss>