hugo-theme-relearn/pir/cont/index.xml

65 lines
6.3 KiB
XML
Raw Normal View History

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Rambl&#39;n on Cap&#39;n Hugo Relearrrn Theme</title>
<link>https://McShelby.github.io/hugo-theme-relearn/pir/cont/index.html</link>
<description>Recent content in Rambl&#39;n on Cap&#39;n Hugo Relearrrn Theme</description>
<generator>Hugo -- gohugo.io</generator>
<language>pir</language><atom:link href="https://McShelby.github.io/hugo-theme-relearn/pir/cont/index.xml" rel="self" type="application/rss+xml" />
<item>
<title>planks orrrganizat&#39;n</title>
<link>https://McShelby.github.io/hugo-theme-relearn/pir/cont/pages/index.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://McShelby.github.io/hugo-theme-relearn/pir/cont/pages/index.html</guid>
<description>In Cap&#39;n Hugo, planks be th&#39; core o&#39; yer ship. Once it be configured, planks be definitely th&#39; added value t&#39; yer documentat&#39;n ship.
Folders Org&#39;nize yer ship like any other Cap&#39;n Hugo project. Typically, ye will have a rrrambl&#39;n folder wit&#39; all yer planks.
rrrambl&#39;n ├── 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>Arrrchetypes</title>
<link>https://McShelby.github.io/hugo-theme-relearn/pir/cont/archetypes/index.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://McShelby.github.io/hugo-theme-relearn/pir/cont/archetypes/index.html</guid>
<description>Us&#39;n th&#39; command: hugo new [relative new rrrambl&#39;n path], ye can start a rrrambl&#39;n file wit&#39; th&#39; date an&#39; title automatically set. While this be a welcome feature, active writers need more: archetypes. These be preconfigured skeleton planks wit&#39; default frontmatter.
Th&#39; Relearrrn theme defines some few archetypes o&#39; planks but ye be free t&#39; define new ones t&#39; yer lik&#39;n. All can be used at any level o&#39; th&#39; documentat&#39;n, th&#39; only difference be&#39;n th&#39; layout o&#39; th&#39; rrrambl&#39;n.</description>
</item>
<item>
<title>Marrrkdown rules</title>
<link>https://McShelby.github.io/hugo-theme-relearn/pir/cont/markdown/index.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://McShelby.github.io/hugo-theme-relearn/pir/cont/markdown/index.html</guid>
<description>Let&amp;rsquo;s face it: Writ&#39;n rrrambl&#39;n fer th&#39; web be tiresome. WYSIWYG editors help alleviate this task, but they generally result &#39;n horr&#39;ble code, or worse yet, ugly web planks.
Marrrkdown be a better way t&#39; write HTML, without all th&#39; complexities an&#39; ugliness that usually accompanies it.
Some o&#39; th&#39; key benefits be:
Marrrkdown be simple t&#39; learn, wit&#39; minimal extra characters so it&amp;rsquo;s also quicker t&#39; write rrrambl&#39;n. Less chance o&#39; errors when writ&#39;n &#39;n Marrrkdown.</description>
</item>
<item>
<title>Menu extrrra shorrrtcuts</title>
<link>https://McShelby.github.io/hugo-theme-relearn/pir/cont/menushortcuts/index.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://McShelby.github.io/hugo-theme-relearn/pir/cont/menushortcuts/index.html</guid>
<description>Ye can define additional menu entries or shortcuts &#39;n th&#39; navigat&#39;n menu without any link t&#39; rrrambl&#39;n.
Basic configurat&#39;n Edit th&#39; website configurat&#39;n config.toml an&#39; add a [[menu.shortcuts]] entry fer each link yer want t&#39; add.
Example from th&#39; 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 an&#39; i18n</title>
<link>https://McShelby.github.io/hugo-theme-relearn/pir/cont/i18n/index.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://McShelby.github.io/hugo-theme-relearn/pir/cont/i18n/index.html</guid>
<description>Th&#39; Relearrrn theme be fully compat&#39;ble wit&#39; Cap&#39;n Hugo multilingual mode.
Avail&#39;ble languages: Arabic, Simplified Chinese, Traditional Chinese, Czech, Dutch, English, Finnish, French, German, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Polish, Portuguese, Russian, Spanish, Turkish, Vietnamese. Feel free t&#39; contribute! Full support fer languages written right t&#39; left Automatic menu generat&#39;n from multilingual rrrambl&#39;n In-browser language switch&#39;n Basic configurat&#39;n Aft learn&#39;n how Cap&#39;n Hugo handle multilingual websites, define yer languages &#39;n yer config.</description>
</item>
<item>
<title>Taxonomy</title>
<link>https://McShelby.github.io/hugo-theme-relearn/pir/cont/taxonomy/index.html</link>
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://McShelby.github.io/hugo-theme-relearn/pir/cont/taxonomy/index.html</guid>
<description>Th&#39; Relearrrn theme supports Hugo&amp;rsquo;s default taxonomies tag an&#39; category out o&#39; th&#39; box.
Configurat&#39;n Just add tags and/or categories t&#39; any plank. They can be given as a single str&#39;n or an array o&#39; str&#39;ns.
+++ categories = [&amp;#34;taxonomy&amp;#34;, &amp;#34;content&amp;#34;] tags = &amp;#34;tutorial&amp;#34; title = &amp;#34;Taxonomy&amp;#34; +++Behavior Th&#39; tags be displayed at th&#39; top o&#39; th&#39; plank &#39;n alphabetical order.
Th&#39; categories be displayed at th&#39; bottom o&#39; th&#39; plank &#39;n alphabetical order &#39;n th&#39; default implementat&#39;n o&#39; th&#39; theme but can be customized by provid&#39;n yer own content-footer.</description>
</item>
</channel>
</rss>