mirror of
https://github.com/McShelby/hugo-theme-relearn.git
synced 2024-11-30 11:13:06 +00:00
48 lines
No EOL
3.2 KiB
XML
48 lines
No EOL
3.2 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||
<channel>
|
||
<title>Relearn Theme for Hugo on Documentation for Hugo Relearn Theme</title>
|
||
<link>https://McShelby.github.io/hugo-theme-relearn/</link>
|
||
<description>Recent content in Relearn Theme for Hugo on Documentation for Hugo Relearn Theme</description>
|
||
<generator>Hugo -- gohugo.io</generator>
|
||
<language>en</language><atom:link href="https://McShelby.github.io/hugo-theme-relearn/index.xml" rel="self" type="application/rss+xml" />
|
||
<item>
|
||
<title>Basics</title>
|
||
<link>https://McShelby.github.io/hugo-theme-relearn/basics/</link>
|
||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||
<guid>https://McShelby.github.io/hugo-theme-relearn/basics/</guid>
|
||
<description>Chapter 1 Basics Discover what this Hugo theme is all about and the core-concepts behind it.</description>
|
||
</item>
|
||
<item>
|
||
<title>Content</title>
|
||
<link>https://McShelby.github.io/hugo-theme-relearn/cont/</link>
|
||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||
<guid>https://McShelby.github.io/hugo-theme-relearn/cont/</guid>
|
||
<description>Chapter 2 Content Find out how to create and organize your content quickly and intuitively.</description>
|
||
</item>
|
||
<item>
|
||
<title>Shortcodes</title>
|
||
<link>https://McShelby.github.io/hugo-theme-relearn/shortcodes/</link>
|
||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||
<guid>https://McShelby.github.io/hugo-theme-relearn/shortcodes/</guid>
|
||
<description>Chapter 3 Shortcodes Hugo uses Markdown for its simple content format. However, there are a lot of things that Markdown doesn’t support well. You could use pure HTML to expand possibilities.
|
||
But this happens to be a bad idea. Everyone uses Markdown because it&rsquo;s pure and simple to read even non-rendered. You should avoid HTML to keep it as simple as possible.
|
||
To avoid this limitations, Hugo created shortcodes. A shortcode is a simple snippet inside a page.</description>
|
||
</item>
|
||
<item>
|
||
<title>This could be yours</title>
|
||
<link>https://McShelby.github.io/hugo-theme-relearn/yours/</link>
|
||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||
<guid>https://McShelby.github.io/hugo-theme-relearn/yours/</guid>
|
||
<description>Chapter 4 This could be yours Start your success story. Now!</description>
|
||
</item>
|
||
<item>
|
||
<title>Tests</title>
|
||
<link>https://McShelby.github.io/hugo-theme-relearn/tests/</link>
|
||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||
<guid>https://McShelby.github.io/hugo-theme-relearn/tests/</guid>
|
||
<description>Chapter 5 Tests Some pages for internal testing of differnt styles
|
||
Code Some testing for different styles used in syntax highlightning and preformatted blocks. Inline Code This is some very long inline code. Where does it wrap? What about wrapping short inline code if multiple sections are written side by side? What about wrapping short inline code if multiple sections are written side/by/side? What about wrapping long inline code if multiple sections are written side567 by34567 side567?</description>
|
||
</item>
|
||
</channel>
|
||
</rss> |