<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Oink Blog on OINK</title>
    <link>https://oink.pgsty.com/blog/oink/</link>
    <description>Recent content in Oink Blog on OINK</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    
    
    
      <lastBuildDate>Fri, 14 Aug 2026 21:56:46 +0800</lastBuildDate>
    
    
      <atom:link href="https://oink.pgsty.com/blog/oink/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>Introducing the OINK implementation preview</title>
        <link>https://oink.pgsty.com/blog/oink/oink-announcement/</link>
        <pubDate>Sat, 08 Aug 2026 00:00:00 +0000</pubDate>
        
        <guid>https://oink.pgsty.com/blog/oink/oink-announcement/</guid>
        <description>&lt;p&gt;Today we are publishing the OINK implementation preview: a directly evolved&#xA;Docsy theme with one canonical product shell, a Hugo-only consumer build,&#xA;local-first browser dependencies, a general multilingual framework, and a set of&#xA;reusable content components drawn from PGSTY documentation sites.&lt;/p&gt;&#xA;&lt;p&gt;This is an implementation and documentation milestone, not a public versioned&#xA;release. The final public brand, module and package identities, first version,&#xA;and production Cloudflare Pages deployment remain explicit release gates.&lt;/p&gt;</description>
      </item>
    <item>
        <title>OINK implementation diary: from copied shells to one theme</title>
        <link>https://oink.pgsty.com/blog/oink/oink-implementation-diary/</link>
        <pubDate>Sat, 08 Aug 2026 00:00:00 +0000</pubDate>
        
        <guid>https://oink.pgsty.com/blog/oink/oink-implementation-diary/</guid>
        <description>&lt;p&gt;OINK began with an awkward observation: several production documentation sites&#xA;looked related because they were related, but their common implementation lived&#xA;as copied files. The visible result was consistent enough; the maintenance model&#xA;was not.&lt;/p&gt;&#xA;&lt;p&gt;This diary records how the project moved from repeated site overrides to one&#xA;directly evolved theme. It focuses on decisions and evidence rather than a&#xA;commit-by-commit transcript.&lt;/p&gt;&#xA;&lt;h2 id=&#34;locking-the-contract&#34;&gt;Locking the contract&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#locking-the-contract&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;The first useful work was subtraction. We wrote down what the product must be&#xA;before choosing how to implement it:&lt;/p&gt;</description>
      </item>
    
  </channel>
</rss>
