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