<metaname="description"content="5.23.0 (2023-11-03) Change Change With 0.120.0 the author settings move into the [params] array in your hugo.toml. Because this collides with the previous way, the theme expected author information, it now adheres to Hugo standards and prints out a warning during built if something is wrong.">
<metaname="twitter:title"content="Version 5.23 :: Hugo Relearn Theme">
<metaname="twitter:description"content="5.23.0 (2023-11-03) Change Change With 0.120.0 the author settings move into the [params] array in your hugo.toml. Because this collides with the previous way, the theme expected author information, it now adheres to Hugo standards and prints out a warning during built if something is wrong.">
<metaproperty="og:title"content="Version 5.23 :: Hugo Relearn Theme">
<metaproperty="og:description"content="5.23.0 (2023-11-03) Change Change With 0.120.0 the author settings move into the [params] array in your hugo.toml. Because this collides with the previous way, the theme expected author information, it now adheres to Hugo standards and prints out a warning during built if something is wrong.">
<metaitemprop="name"content="Version 5.23 :: Hugo Relearn Theme">
<metaitemprop="description"content="5.23.0 (2023-11-03) Change Change With 0.120.0 the author settings move into the [params] array in your hugo.toml. Because this collides with the previous way, the theme expected author information, it now adheres to Hugo standards and prints out a warning during built if something is wrong.">
<p><spanclass="badge cstyle note badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-exclamation-circle"></i></span><spanclass="badge-content">Change</span></span> Change of behavior, may require action</p>
</li>
<li>
<p><spanclass="badge cstyle info badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-plus-circle"></i></span><spanclass="badge-content">New</span></span> New behavior, often introducing new options</p>
</li>
</ul>
<hr>
<h2id="5-23-0">5.23.0 (2023-11-03)</h2>
<h3id="change">Change</h3>
<ul>
<li>
<p><spanclass="badge cstyle note badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-exclamation-circle"></i></span><spanclass="badge-content">Change</span></span> With <spanclass="badge cstyle default badge-with-title"><spanclass="badge-title"><iclass="fa-fw fab fa-hackerrank"></i></span><spanclass="badge-content"style="background-color: fuchsia;">0.120.0</span></span> the author settings move into the <code>[params]</code> array in your <code>hugo.toml</code>. Because this collides with the previous way, the theme expected author information, it now adheres to Hugo standards and prints out a warning during built if something is wrong.</p>
<p><spanclass="badge cstyle note badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-exclamation-circle"></i></span><spanclass="badge-content">Change</span></span> Taxonomy <ahref="https://gohugo.io/content-management/taxonomies#add-custom-metadata-to-a-taxonomy-or-term"rel="external"target="_self">term pages</a> now add the breadcrumb for each listed page. If this gets too crowded for you, you can turn the breadcrumbs off in your <code>hugo.toml</code> by adding <code>disableTermBreadcrumbs=true</code>.</p>
</li>
</ul>
<h3id="new">New</h3>
<ul>
<li>
<p><spanclass="badge cstyle info badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-plus-circle"></i></span><spanclass="badge-content">New</span></span> Taxonomy and term pages are now allowed to contain content. This is added inbetween the title and the page list.</p>
</li>
<li>
<p><spanclass="badge cstyle info badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-plus-circle"></i></span><spanclass="badge-content">New</span></span> It is now possible to print custom taxonomies anywhere in your page. <ahref="/hugo-theme-relearn/configuration/customization/taxonomy/index.html#setting-up-custom-taxonomies">See the docs</a>.</p>
</li>
<li>
<p><spanclass="badge cstyle info badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-plus-circle"></i></span><spanclass="badge-content">New</span></span> It is now possible to adjust the menu width for your whole site. <ahref="/hugo-theme-relearn/configuration/sidebar/width/index.html">See the docs</a>.</p>
</li>
<li>
<p><spanclass="badge cstyle info badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-plus-circle"></i></span><spanclass="badge-content">New</span></span> This release adds social media meta tags for the Open Graph protocol and Twitter Cards to your site. <ahref="/hugo-theme-relearn/authoring/meta/index.html">See the docs</a>.</p>
</li>
<li>
<p><spanclass="badge cstyle info badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-plus-circle"></i></span><spanclass="badge-content">New</span></span> This release comes with additional sort options for the menu and the <ahref="/hugo-theme-relearn/shortcodes/children/index.html"><code>children</code> shortcode</a>. Both will now accept the following values: <code>weight</code>, <code>title</code>, <code>linktitle</code>, <code>modifieddate</code>, <code>expirydate</code>, <code>publishdate</code>, <code>date</code>, <code>length</code> or <code>default</code> (adhering to Hugo’s default sort order).</p>
</li>
<li>
<p><spanclass="badge cstyle info badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-plus-circle"></i></span><spanclass="badge-content">New</span></span> The theme now provides a mechanism to load further JavaScript dependencies defined by you only if it is needed. This comes in handy if you want to add own shortcodes that depend on additional JavaScript code to be loaded. <ahref="/hugo-theme-relearn/configuration/customization/dependencies/index.html">See the docs</a>.</p>
</li>
<li>
<p><spanclass="badge cstyle info badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-plus-circle"></i></span><spanclass="badge-content">New</span></span> The theme has updated its Mermaid dependency to 10.6.0. This adds support for the <ahref="/hugo-theme-relearn/shortcodes/mermaid/index.html#xychart">xychart type</a>.</p>
</li>
<li>
<p><spanclass="badge cstyle info badge-with-title"><spanclass="badge-title"><iclass="fa-fw fas fa-plus-circle"></i></span><spanclass="badge-content">New</span></span> This release adds portable Markdown links.</p>
<p>Previously it was not possible to use pure Markdown links in a configuration independent way to link to pages inside of your project. It always required you to know how your <code>uglyURLs</code> setting is, wheather you link to a page or page bundle and in case of relative links if your current page is a page or page bundle. (eg. <code>[generator](generator/index.html)</code> vs. <code>[generator](generator.html)</code>). This is a hassle as you have to change these links manually once you change your <code>uglyURLs</code> setting or change the type of a page.</p>
<p>You could work around this by using the <code>relref</code> shortcode (eg <code>[generator]({{% relref "../generator" %}})</code>) which works but results in non-portable Markdown.</p>
<p>Now it’s possible to use the same path of a call to <code>relref</code> in a plain Markdown link (eg <code>[generator](../generator)</code>). This is independent of any configuration settings or the page types involved in linking. Note, that this requires your links to be given without any extension, so <code>[generator](generator/index.html)</code> will work as before.</p>
<p>The following types of linking are supported:</p>
