<?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 Docsy</title><link>https://deploy-preview-2525--docsydocs.netlify.app/xx/docs/best-practices/</link><description>Recent content in Best Practices on Docsy</description><generator>Hugo</generator><language>xx</language><atom:link href="https://deploy-preview-2525--docsydocs.netlify.app/xx/docs/best-practices/index.xml" rel="self" type="application/rss+xml"/><item><title>Hugo Content Tips</title><link>https://deploy-preview-2525--docsydocs.netlify.app/xx/docs/best-practices/site-guidance/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-2525--docsydocs.netlify.app/xx/docs/best-practices/site-guidance/</guid><description>&lt;p&gt;Docsy is a theme for the &lt;a href="https://gohugo.io/"&gt;Hugo&lt;/a&gt; static site generator. If
you&amp;rsquo;re not already familiar with Hugo this page provides some useful tips and
potential gotchas for adding and editing content for your site. Feel free to add
your own!&lt;/p&gt;
&lt;h2 id="linking"&gt;Linking&lt;a class="td-heading-self-link" href="#linking" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;By default, regular relative URLs in links are left unchanged by Hugo (they&amp;rsquo;re
still relative links in your site&amp;rsquo;s generated HTML), hence some hardcoded
relative links like &lt;code&gt;[relative cross-link](../../peer-folder/sub-file.md)&lt;/code&gt; might
behave unexpectedly compared to how they work on your local file system. You may
find it helpful to use some of Hugo&amp;rsquo;s built-in link shortcodes like
&lt;a href="https://gohugo.io/shortcodes/relref/"&gt;relref&lt;/a&gt; to avoid broken links in your
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
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://deploy-preview-2525--docsydocs.netlify.app/xx/docs/best-practices/organizing-content/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-2525--docsydocs.netlify.app/xx/docs/best-practices/organizing-content/</guid><description>&lt;p&gt;If you have a look at our &lt;a href="https://example.docsy.dev/about/"&gt;Example Site&lt;/a&gt;,
you&amp;rsquo;ll see that we&amp;rsquo;ve organized the Documentation section into a number of
subsections, each with some recommendations about what you might put in that
section.&lt;/p&gt;
&lt;h2 id="do-i-need-to-use-this-structure"&gt;Do I need to use this structure?&lt;a class="td-heading-self-link" href="#do-i-need-to-use-this-structure" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Absolutely not! The site structure in the Example Site was created to meet the
needs of large docsets for large products with lots of features, potential
tasks, and reference elements. For a simpler docset (like this one!), it&amp;rsquo;s fine
to just structure your docs around specific features that your users need to
know about. Even for larger documentation sets, you may find that the structure
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>