<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Comments on YHY Study Website</title><link>https://ryan.0412.online/en/tags/comments/</link><description>Recent content in Comments on YHY Study Website</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 30 Sep 2026 23:51:06 +0800</lastBuildDate><atom:link href="https://ryan.0412.online/en/tags/comments/index.xml" rel="self" type="application/rss+xml"/><item><title>How Hugo and Oink Integrate Giscus Comments</title><link>https://ryan.0412.online/en/blog/hugo-oink-giscus-comments/</link><pubDate>Wed, 30 Sep 2026 00:00:00 +0000</pubDate><guid>https://ryan.0412.online/en/blog/hugo-oink-giscus-comments/</guid><description>&lt;p&gt;Hugo produces static HTML. It does not provide a server that accepts comments, a database, or a user system. Adding comments to a Hugo site with Oink therefore means delegating the comment interface to Giscus and storing the data in GitHub Discussions.&lt;/p&gt;
&lt;p&gt;When I added comments to the site, I wanted one conversation for everyone—whether they opened the Chinese or English page, on Vercel or GitHub Pages. Here&amp;rsquo;s how the pieces work together to bring a comment onto a static blog page.&lt;/p&gt;</description></item></channel></rss>