<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Best Practices on OINK</title>
		<link>https://oink.pgsty.com/docs/best-practices/</link>
		<description>Recent content in Best Practices on OINK</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<atom:link href="https://oink.pgsty.com/docs/best-practices/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Hugo Content Tips</title>
				<link>https://oink.pgsty.com/docs/best-practices/site-guidance/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://oink.pgsty.com/docs/best-practices/site-guidance/</guid>
				<description>&lt;p&gt;Docsy is a theme for the &lt;a href=&#34;https://gohugo.io/&#34;&gt;Hugo&lt;/a&gt; static site generator. If&#xA;you&amp;rsquo;re not already familiar with Hugo this page provides some useful tips and&#xA;potential gotchas for adding and editing content for your site. Feel free to add&#xA;your own!&lt;/p&gt;&#xA;&lt;h2 id=&#34;linking&#34;&gt;Linking&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#linking&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;By default, regular relative URLs in links are left unchanged by Hugo (they&amp;rsquo;re&#xA;still relative links in your site&amp;rsquo;s generated HTML), hence some hardcoded&#xA;relative links like &lt;code&gt;[relative cross-link](../../peer-folder/sub-file.md)&lt;/code&gt; might&#xA;behave unexpectedly compared to how they work on your local file system. You may&#xA;find it helpful to use some of Hugo&amp;rsquo;s built-in link shortcodes like&#xA;&lt;a href=&#34;https://gohugo.io/shortcodes/relref/&#34;&gt;relref&lt;/a&gt; to avoid broken links in your&#xA;generated site. For example a &lt;code&gt;{{&amp;lt; ref &amp;quot;filename.md&amp;quot; &amp;gt;}}&lt;/code&gt; link in Hugo will&#xA;actually find and automatically link to your file named &lt;code&gt;filename.md&lt;/code&gt;.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Organizing Your Content</title>
				<link>https://oink.pgsty.com/docs/best-practices/organizing-content/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://oink.pgsty.com/docs/best-practices/organizing-content/</guid>
				<description>&lt;p&gt;If you have a look at our &lt;a href=&#34;https://example.docsy.dev/about/&#34;&gt;Example Site&lt;/a&gt;,&#xA;you&amp;rsquo;ll see that we&amp;rsquo;ve organized the Documentation section into a number of&#xA;subsections, each with some recommendations about what you might put in that&#xA;section.&lt;/p&gt;&#xA;&lt;h2 id=&#34;do-i-need-to-use-this-structure&#34;&gt;Do I need to use this structure?&lt;a class=&#34;td-heading-self-link&#34; href=&#34;#do-i-need-to-use-this-structure&#34; aria-label=&#34;Heading self-link&#34;&gt;&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;Absolutely not! The site structure in the Example Site was created to meet the&#xA;needs of large docsets for large products with lots of features, potential&#xA;tasks, and reference elements. For a simpler docset (like this one!), it&amp;rsquo;s fine&#xA;to just structure your docs around specific features that your users need to&#xA;know about. Even for larger documentation sets, you may find that the structure&#xA;isn&amp;rsquo;t useful &amp;ldquo;as is&amp;rdquo;, or that you don&amp;rsquo;t need to use all the section types.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
