<lidata-nav-id=/cont/menushortcuts/title="Menu extra shortcuts"class=dd-item><ahref=../../cont/menushortcuts/>Menu extra shortcuts<iclass="fas fa-check read-icon"></i></a></li>
<lidata-nav-id=/cont/icons/title="Icons and logos"class=dd-item><ahref=../../cont/icons/>Icons and logos<iclass="fas fa-check read-icon"></i></a></li>
<lidata-nav-id=/cont/i18n/title="Multilingual and i18n"class="dd-item alwaysopen"><ahref=../../cont/i18n/>Multilingual and i18n<iclass="fas fa-check read-icon"></i></a><ul></ul></li>
<aclass=github-buttonhref=https://github.com/McShelby/hugo-theme-relearn/archive/main.zipdata-icon=octicon-cloud-downloadaria-label="Download McShelby/hugo-theme-relearn on GitHub">Download</a>
<aclass=github-buttonhref=https://github.com/McShelby/hugo-theme-relearndata-icon=octicon-stardata-show-count=truearia-label="Star McShelby/hugo-theme-relearn on GitHub">Star</a>
<aclass=github-buttonhref=https://github.com/McShelby/hugo-theme-relearn/forkdata-icon=octicon-repo-forkeddata-show-count=truearia-label="Fork McShelby/hugo-theme-relearn on GitHub">Fork</a>
<p>Built with <ahref=https://github.com/McShelby/hugo-theme-relearn><iclass="fas fa-heart"></i></a> by <ahref=https://gohugo.io/>Hugo</a></p>
<aclass=github-linktitle="Edit this page"href=https://github.com/McShelby/hugo-theme-relearn/edit/main/exampleSite/content/basics/migration/_index.en.mdtarget=blank>
<iclass="fas fa-code-branch"></i>
<spanid=top-github-link-text>Edit this page</span>
<p>This document shows you what’s new in the latest release. For a detailed list of changes, see the <ahref=../../basics/history/>history page</a>.</p>
<p><strong>Breaking</strong>: This release removes the themes implementation of <code>ref</code>/<code>relref</code> in favor for Hugos standard implementation. This is because of inconsistencies with the themes implementation. In advantage, your project becomes standard complient and exchanging this theme in your project to some other theme will be effortless.</p>
<p>In a standard complient form you must not link to the <code>*.md</code> file but to its logical name. You’ll see, referencing other pages becomes much easier. All three types result in the same reference:</p>
<p>If you’ve linked from a page of one language to a page of another language, conversion is a bit more difficult but <ahref=https://gohugo.io/content-management/cross-references/#link-to-another-language-version>Hugo got you covered</a> as well.</p>
<p>Also, the old themes implementation allowed refs to non-existing content. This will cause Hugos implementation to show the error below and abort the generation. If your project relies on this old behavior, you can <ahref=https://gohugo.io/content-management/cross-references/#link-to-another-language-version>reconfigure the error handling</a> of Hugos implementation.</p>
<p>In the best case your usage of the old implementation is already standard complient and you don’t need to change anything. You’ll notice this very easily once you’ve started <code>hugo server</code> after an upgrade and no errors are written to the console.</p>
<p>You may see errors on the console after the update in the form:</p>
<divclass=highlight><pretabindex=0style=color:#e2e4e5;background-color:#282a36;-moz-tab-size:4;-o-tab-size:4;tab-size:4><codeclass=language-shdata-lang=sh>ERROR 2021/11/19 22:29:10 <spanstyle=color:#ff6ac1>[</span>en<spanstyle=color:#ff6ac1>]</span> REF_NOT_FOUND: Ref <spanstyle=color:#5af78e>"basics/configuration/_index.md"</span>: <spanstyle=color:#5af78e>"hugo-theme-relearn\exampleSite\content\_index.en.md:19:22"</span>: page not found
</code></pre></div><p>In this case, you must apply one of two options:</p>
<ol>
<li>
<p>Copy the old implementation files <code>theme/hugo-theme-relearn/layouts/shortcode/ref.html</code> and <code>theme/hugo-theme-relearn/layouts/shortcode/relref.html</code> to your own projects <code>layouts/shortcode/ref.html</code> and <code>layouts/shortcode/relref.html</code> respectively. <strong>This is not recommended</strong> as your project will still rely on non-standard behavior afterwards.</p>
</li>
<li>
<p>Start up a text editor with regular expression support for search and replace. Apply the following conversions in the given order on all <code>*.md</code> files. <strong>This is the recommended choice</strong>.</p>
<p><strong>Change</strong>: Although never officially documented, this release removes the font <code>Novacento</code>/<code>Novecento</code> from the release. If you use it in an overwritten CSS please replace it with <code>Work Sans</code>. This change was necessary as Novacento did not provide all Latin special characters and lead to mixed styled character text eg. for czech.</p>
<p><strong>New</strong>: The theme now supports favicons served from <code>static/images/</code> named as <code>favicon</code> or <code>logo</code> in SVG, PNG or ICO format <ahref=../../basics/customization/#change-the-favicon>out of the box</a>. An overridden partial <code>layouts/partials/favicon.html</code> may not be necessary anymore in most cases.</p>
</li>
<li>
<p><strong>New</strong>: You can hide the table of contents menu for the whole site by setting the <code>disableToc</code> option in your <code>config.toml</code>. For an example see <ahref=../../basics/configuration/#global-site-parameters>the example configuration</a>.</p>
<li><strong>New</strong>: Optional second parameter for <ahref=../../shortcodes/notice/><code>notice</code></a> shortcode to set title in box header.</li>
<li><strong>New</strong>: Your site can now be served from a subfolder if you set <code>baseURL</code> and <code>canonifyURLs=true</code> in your <code>config.toml</code>. See the <ahref=../../basics/configuration/#a-word-on-running-your-site-in-a-subfolder>documentation</a> for a detailed example.</li>
<li><strong>Change</strong>: Add new colors <code>--MAIN-CODE-color</code> and <code>--MAIN-CODE-BG-color</code> for syntax highlightning fallback in your stylesheet in case <code>guessSyntax=true</code> is set. Ideally they are set to the same values as the ones from your chosen chroma style.</li>
<p><strong>Change</strong>: Creation of customized stylesheets was simplified down to only contain the CSS variables. Everything else can and should be deleted from your custom stylesheet to assure everything works fine. For the predefined stylesheet variants, this change is already included. The <ahref=../../basics/customization/#mine-variant>documentation</a> was adjusted accordingly.</p>
<p><strong>New</strong>: Hidden pages are displayed by default in their according tags page. You can now turn off this behavior by setting <code>disableTagHiddenPages=true</code> in your <code>config.toml</code>.</p>
<p><strong>New</strong>: You can define the expansion state of your menus for the whole site by setting the <code>alwaysopen</code> option in your <code>config.toml</code>. Please see further <ahref=../../cont/pages/#override-expand-state-rules-for-menu-entries>documentation</a> for possible values and default behavior.</p>
<p><strong>New</strong>: New frontmatter <code>ordersectionsby</code> option to change immediate children sorting in menu and <code>children</code> shortcode. Possible values are <code>title</code> or <code>weight</code>.</p>
</li>
<li>
<p><strong>New</strong>: Alternate content of a page is now advertised in the HTML meta tags. See <ahref=https://gohugo.io/templates/rss/#reference-your-rss-feed-in-head>Hugo documentation</a>.</p>
</li>
</ul>
<hr>
<h2id=220>2.2.0</h2>
<ul>
<li><strong>New</strong>: Hidden pages are displayed by default in the sitemap generated by Hugo and are therefore visible for search engine indexing. You can now turn off this behavior by setting <code>disableSeoHiddenPages=true</code> in your <code>config.toml</code>.</li>
</ul>
<hr>
<h2id=210>2.1.0</h2>
<ul>
<li>
<p><strong>Change</strong>: In case the site’s structure contains addional *.md files not part of the site (eg files that are meant to be included by site pages - see CHANGELOG.md in exampleSite), they will now be ignored by the search.</p>
</li>
<li>
<p><strong>New</strong>: Hidden pages are indexed for the site search by default. You can now turn off this behavior by setting <code>disableSearchHiddenPages=true</code> in your <code>config.toml</code>.</p>
</li>
<li>
<p><strong>New</strong>: If a search term is found in an <code>expand</code> shortcode, the expand will be opened.</p>
</li>
<li>
<p><strong>New</strong>: The menu will scroll the active item into view on load.</p>
</li>
</ul>
<hr>
<h2id=200>2.0.0</h2>
<ul>
<li>
<p><strong>Change</strong>: Syntaxhighlightning was switched to <ahref=https://gohugo.io/content-management/syntax-highlighting/>built in Hugo mechanism</a>. You may need to configure a new stylesheet or decide to roll you own as describedd on in the Hugo documentation</p>
</li>
<li>
<p><strong>Change</strong>: In the predefined stylesheets there was a typo and <code>--MENU-HOME-LINK-HOVERED-color</code> must be changed to <code>--MENU-HOME-LINK-HOVER-color</code>.</p>
</li>
<li>
<p><strong>Change</strong>: <code>--MENU-HOME-LINK-color</code> and <code>--MENU-HOME-LINK-HOVER-color</code> were missing in the documentation. You should add them to your custom stylesheets.</p>
</li>
<li>
<p><strong>Change</strong>: Arrow navigation and <code>children</code> shortcode were ignoring setting for <code>ordersectionsby</code>. This is now changed and may result in different sorting order of your sub pages.</p>
</li>
<li>
<p><strong>Change</strong>: If hidden pages are accessed directly by typing their URL, they will be exposed in the menu.</p>
</li>
<li>
<p><strong>Change</strong>: A page without a <code>title</code> will be treated as <code>hidden=true</code>.</p>
<p><strong>New</strong>: You can define the expansion state of your menus in the frontmatter. Please see further <ahref=../../cont/pages/#override-expand-state-rules-for-menu-entries>documentation</a> for possible values and default behavior.</p>
<p><strong>New</strong>: New partials for defining pre/post content for menu items and the content. See <ahref=../../basics/customization/>documentation</a> for further reading.</p>
<li><strong>New</strong>: <ahref=../../shortcodes/mermaid/#configuration><code>Mermaid</code></a> config options can be set in <code>config.toml</code>.</li>
