hugo-theme-relearn/cont/index.xml

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Content on Hugo Relearn Theme</title>
    <link>https://McShelby.github.io/hugo-theme-relearn/cont/index.html</link>
    <description>Recent content in Content on Hugo Relearn Theme</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://McShelby.github.io/hugo-theme-relearn/cont/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pages organization</title>
      <link>https://McShelby.github.io/hugo-theme-relearn/cont/pages/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://McShelby.github.io/hugo-theme-relearn/cont/pages/index.html</guid>
      <description>In Hugo, pages are the core of your site. Once it is configured, pages are definitely the added value to your documentation site.
Folders Organize your site like any other Hugo project. Typically, you will have a content folder with all your pages.
content ├── level-one │ ├── level-two │ │ ├── level-three │ │ │ ├── level-four │ │ │ │ ├── _index.md &amp;lt;-- /level-one/level-two/level-three/level-four │ │ │ │ ├── page-4-a.</description>
    </item>
    <item>
      <title>Archetypes</title>
      <link>https://McShelby.github.io/hugo-theme-relearn/cont/archetypes/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://McShelby.github.io/hugo-theme-relearn/cont/archetypes/index.html</guid>
      <description>Using the command: hugo new [relative new content path], you can start a content file with the date and title automatically set. While this is a welcome feature, active writers need more: archetypes. These are preconfigured skeleton pages with default frontmatter.
The Relearn theme defines some few archetypes of pages but you are free to define new ones to your liking. All can be used at any level of the documentation, the only difference being the layout of the content.</description>
    </item>
    <item>
      <title>Markdown syntax</title>
      <link>https://McShelby.github.io/hugo-theme-relearn/cont/markdown/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://McShelby.github.io/hugo-theme-relearn/cont/markdown/index.html</guid>
      <description>Let&amp;rsquo;s face it: Writing content for the web is tiresome. WYSIWYG editors help alleviate this task, but they generally result in horrible code, or worse yet, ugly web pages.
Markdown is a better way to write HTML, without all the complexities and ugliness that usually accompanies it.
Some of the key benefits are:
Markdown is simple to learn, with minimal extra characters so it&amp;rsquo;s also quicker to write content. Less chance of errors when writing in Markdown.</description>
    </item>
    <item>
      <title>Menu extra shortcuts</title>
      <link>https://McShelby.github.io/hugo-theme-relearn/cont/menushortcuts/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://McShelby.github.io/hugo-theme-relearn/cont/menushortcuts/index.html</guid>
      <description>You can define additional menu entries or shortcuts in the navigation menu without any link to content.
Basic configuration Edit the website configuration config.toml and add a [[menu.shortcuts]] entry for each link your want to add.
Example from the current website:
[[menu.shortcuts]] name = &amp;#34;&amp;lt;i class=&amp;#39;fab fa-fw fa-github&amp;#39;&amp;gt;&amp;lt;/i&amp;gt; GitHub repo&amp;#34; identifier = &amp;#34;ds&amp;#34; url = &amp;#34;https://github.com/McShelby/hugo-theme-relearn&amp;#34; weight = 10 [[menu.shortcuts]] name = &amp;#34;&amp;lt;i class=&amp;#39;fas fa-fw fa-camera&amp;#39;&amp;gt;&amp;lt;/i&amp;gt; Showcases&amp;#34; url = &amp;#34;showcase/&amp;#34; weight = 11 [[menu.</description>
    </item>
    <item>
      <title>Multilingual and i18n</title>
      <link>https://McShelby.github.io/hugo-theme-relearn/cont/i18n/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://McShelby.github.io/hugo-theme-relearn/cont/i18n/index.html</guid>
      <description>The Relearn theme is fully compatible with Hugo multilingual mode.
Available languages: Arabic, Simplified Chinese, Traditional Chinese, Czech, Dutch, English, Finnish French, German, Hindi, Indonesian, Italian, Japanese, Korean, Polish, Portuguese, Russian, Spanish, Turkish, Vietnamese. Feel free to contribute! Full support for languages written right to left Automatic menu generation from multilingual content In-browser language switching Basic configuration After learning how Hugo handle multilingual websites, define your languages in your config.toml file.</description>
    </item>
    <item>
      <title>Taxonomy</title>
      <link>https://McShelby.github.io/hugo-theme-relearn/cont/taxonomy/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://McShelby.github.io/hugo-theme-relearn/cont/taxonomy/index.html</guid>
      <description>The Relearn theme supports Hugo&amp;rsquo;s default taxonomies tag and category out of the box.
Configuration Just add tags and/or categories to any page. They can be given as a single string or an array of strings.
+++ categories = [&amp;#34;taxonomy&amp;#34;, &amp;#34;content&amp;#34;] tags = &amp;#34;tutorial&amp;#34; title = &amp;#34;Taxonomy&amp;#34; +++Behavior The tags are displayed at the top of the page in alphabetical order.
The categories are displayed at the bottom of the page in alphabetical order in the default implementation of the theme but can be customized by providing your own content-footer.</description>
    </item>
  </channel>
</rss>