<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Update OINK on OINK</title>
		<link>https://oink.pgsty.com/docs/update/</link>
		<description>Recent content in Update OINK on OINK</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<atom:link href="https://oink.pgsty.com/docs/update/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Update the OINK Hugo module</title>
				<link>https://oink.pgsty.com/docs/update/hugo-module/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://oink.pgsty.com/docs/update/hugo-module/</guid>
				<description>&lt;h2 id=&#34;pin-a-version&#34;&gt;Pin a version&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#pin-a-version&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Production sites should import a release tag or immutable commit, never an&#xA;unversioned branch. From the site root, update Oink to a specific ref:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;hugo mod get github.com/pgsty/oink@THEME_REF&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;hugo mod tidy&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Replace &lt;code&gt;THEME_REF&lt;/code&gt; with the published root tag or commit named by the release.&lt;/p&gt;&#xA;&lt;h2 id=&#34;test-a-local-checkout&#34;&gt;Test a local checkout&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#test-a-local-checkout&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;To test the current OINK checkout without changing the committed module path,&#xA;use an ignored Go workspace with the local theme checkout:&lt;/p&gt;</description>
			</item>
			<item>
				<title>Migrate from the Docsy npm package</title>
				<link>https://oink.pgsty.com/docs/update/npm-package/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://oink.pgsty.com/docs/update/npm-package/</guid>
				<description>&lt;p&gt;The upstream &lt;code&gt;@docsy/theme&lt;/code&gt; npm package is not an OINK distribution channel.&#xA;OINK ships Bootstrap, Font Awesome, fonts, and browser runtimes directly with&#xA;the theme so that consumer sites build with Hugo Extended alone.&lt;/p&gt;&#xA;&lt;h2 id=&#34;remove-the-npm-theme-integration&#34;&gt;Remove the npm theme integration&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#remove-the-npm-theme-integration&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;First select an OINK distribution: a versioned archive, Git submodule or clone,&#xA;or the compatibility Hugo module. Make that theme available to Hugo and confirm&#xA;that &lt;code&gt;hugo --gc --minify&lt;/code&gt; can resolve it.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Update an OINK Git submodule or clone</title>
				<link>https://oink.pgsty.com/docs/update/git/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://oink.pgsty.com/docs/update/git/</guid>
				<description>&lt;p&gt;Use the procedure matching the installation: &lt;a href=&#34;https://oink.pgsty.com/docs/update/git/#update-the-submodule&#34;&gt;submodule&lt;/a&gt;&#xA;or &lt;a href=&#34;https://oink.pgsty.com/docs/update/git/#update-the-clone&#34;&gt;clone&lt;/a&gt;. Pin the target release tag or immutable commit in&#xA;both cases.&lt;/p&gt;&#xA;&lt;h2 id=&#34;update-the-submodule&#34;&gt;Update the submodule&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#update-the-submodule&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;From the site root, fetch tags inside the theme and check out the target ref:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;git -C themes/oink fetch --tags&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;git -C themes/oink checkout THEME_REF&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;git add themes/oink&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;git commit -m &lt;span class=&#34;s2&#34;&gt;&amp;#34;Update OINK theme to THEME_REF&amp;#34;&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Replace &lt;code&gt;themes/oink&lt;/code&gt; if the site uses another directory name. The parent&#xA;repository records the resulting submodule commit. Push that parent commit so CI&#xA;and other contributors resolve the same source.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Migrate a Docsy site to OINK</title>
				<link>https://oink.pgsty.com/docs/update/convert-site-to-module/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://oink.pgsty.com/docs/update/convert-site-to-module/</guid>
				<description>&lt;p&gt;This migration removes copied common shell overrides and the consumer-side npm&#xA;asset pipeline. It does not require a bulk rewrite of Markdown content.&lt;/p&gt;&#xA;&lt;h2 id=&#34;before-you-begin&#34;&gt;Before you begin&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#before-you-begin&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Create a branch and make sure the existing site builds. Inventory custom files&#xA;under &lt;code&gt;layouts/&lt;/code&gt;, &lt;code&gt;assets/&lt;/code&gt;, &lt;code&gt;static/&lt;/code&gt;, and &lt;code&gt;i18n/&lt;/code&gt;, classifying each as:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;common Docsy shell code now supplied by OINK;&lt;/li&gt;&#xA;&lt;li&gt;a reusable component now supplied by OINK;&lt;/li&gt;&#xA;&lt;li&gt;a site-owned brand, product page, or business component that must remain.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Do not delete the third category.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
