Initial check-in after refactoring to use Hugo site generator with ReLearn template. HTTP Status Codes page not done--nor adwords added.

themes/relearn/exampleSite/content/cont/_index.en.md

@@ -0,0 +1,11 @@
++++
+chapter = true
+title = "Content"
+weight = 2
++++
+
+### Chapter 2
+
+# Content
+
+Find out how to create and organize your content quickly and intuitively.

themes/relearn/exampleSite/content/cont/_index.pir.md

@@ -0,0 +1,6 @@
++++
+chapter = true
+title = "Rambl'n"
+weight = 2
++++
+{{< piratify >}}

themes/relearn/exampleSite/content/cont/archetypes.en.md

@@ -0,0 +1,58 @@
++++
+title = "Archetypes"
+weight = 10
++++
+
+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](https://gohugo.io/content/archetypes/).
+
+It is pre-configured skeleton pages with default front matter. Please refer to the documentation for types of page to understand the differences.
+
+## Chapter {#archetypes-chapter}
+
+To create a Chapter page, run the following commands
+
+```shell
+hugo new --kind chapter <name>/_index.md
+```
+
+It will create a page with predefined Front-Matter:
+
+```toml
++++
+chapter = true
+pre = "<b>X. </b>"
+title = "{{ replace .Name "-" " " | title }}"
+weight = 5
++++
+
+### Chapter X
+
+# Some Chapter title
+
+Lorem Ipsum.
+```
+
+## Default
+
+To create a default page, run either one of the following commands either
+
+```shell
+hugo new <chapter>/<name>/_index.md
+```
+
+or
+
+```shell
+hugo new <chapter>/<name>.md
+```
+
+It will create a page with predefined Front-Matter:
+
+```toml
++++
+title = "{{ replace .Name "-" " " | title }}"
+weight = 5
++++
+
+Lorem Ipsum.
+```

themes/relearn/exampleSite/content/cont/archetypes.pir.md

@@ -0,0 +1,5 @@
++++
+title = "Arrrchetypes"
+weight = 10
++++
+{{< piratify >}}

themes/relearn/exampleSite/content/cont/i18n/_index.en.md

@@ -0,0 +1,71 @@
++++
+title = "Multilingual and i18n"
+weight = 30
++++
+
+The Relearn theme is fully compatible with Hugo multilingual mode.
+
+It provides:
+
+- Translation strings for default values (English, Piratized English, Arabic, Simplified Chinese, Traditional Chinesse, Dutch, French, German, Hindi, Indonesian, Italian, Japanese, Korean, Polish, Portuguese, Russian, Spanish, Turkish, Vietnamese). Feel free to contribute!
+- Automatic menu generation from multilingual content
+- In-browser language switching
+
+![I18n menu](images/i18n-menu.gif?classes=shadow&width=300px)
+
+## Basic configuration
+
+After learning [how Hugo handle multilingual websites](https://gohugo.io/content-management/multilingual), define your languages in your `config.toml` file.
+
+For example with current English and Piratized English website.
+
+```toml
+# English is the default language
+defaultContentLanguage = "en"
+
+[Languages]
+[Languages.en]
+title = "Hugo Relearn Theme"
+weight = 1
+languageName = "English"
+
+[Languages.pir]
+title = "Cap'n Hugo Relearrrn Theme"
+weight = 2
+languageName = "Arrr! Pirrrates"
+```
+
+Then, for each new page, append the *id* of the language to the file.
+
+- Single file `my-page.md` is split in two files:
+    - in English: `my-page.md`
+    - in Piratized English: `my-page.pir.md`
+- Single file `_index.md` is split in two files:
+    - in English: `_index.md`
+    - in Piratized English: `_index.pir.md`
+
+{{% notice info %}}
+Be aware that only translated pages are displayed in menu. It's not replaced with default language content.
+{{% /notice %}}
+
+{{% notice tip %}}
+Use [slug](https://gohugo.io/content-management/multilingual/#translate-your-content) Front Matter parameter to translate urls too.
+{{% /notice %}}
+
+## Overwrite translation strings
+
+Translations strings are used for common default values used in the theme (*Edit* button, *Search placeholder* and so on). Translations are available in English and Piratized English but you may use another language or want to override default values.
+
+To override these values, create a new file in your local i18n folder `i18n/<idlanguage>.toml` and inspire yourself from the theme `themes/hugo-theme-relearn/i18n/en.toml`
+
+## Disable language switching
+
+Switching the language in the browser is a great feature, but for some reasons you may want to disable it.
+
+Just set `disableLanguageSwitchingButton=true` in your `config.toml`
+
+```toml
+[params]
+  # When using mulitlingual website, disable the switch language button.
+  disableLanguageSwitchingButton = true
+```

themes/relearn/exampleSite/content/cont/i18n/_index.pir.md

@@ -0,0 +1,5 @@
++++
+title = "Multilingual an' i18n"
+weight = 30
++++
+{{< piratify >}}

themes/relearn/exampleSite/content/cont/icons.en.md

@@ -0,0 +1,41 @@
++++
+title = "Icons and logos"
+weight = 27
++++
+
+The Relearn theme for Hugo loads the [**Font Awesome**](https://fontawesome.com) library, allowing you to easily display any icon or logo available in the Font Awesome free collection.
+
+## Finding an icon
+
+Browse through the available icons in the [Font Awesome Gallery](https://fontawesome.com/v5/search?m=free). Notice that the **free** filter is enabled, as only the free icons are available by default.
+
+Once on the Font Awesome page for a specific icon, for example the page for the [heart](https://fontawesome.com/v5/icons/heart?s=solid), copy the HTML reference and paste into the Markdown content.
+
+The HTML to include the heart icon is:
+
+```html
+<i class="fas fa-heart"></i>
+```
+
+## Including in markdown
+
+Paste the `<i>` HTML into markup and Font Awesome will load the relevant icon.
+
+```html
+Built with <i class="fas fa-heart"></i> by Relearn and Hugo
+```
+
+Which appears as
+
+Built with <i class="fas fa-heart"></i> by Relearn and Hugo
+
+## Customising icons
+
+Font Awesome provides many ways to modify the icon
+
+* Change color (by default the icon will inherit the parent color)
+* Increase or decrease size
+* Rotate
+* Combine with other icons
+
+Check the full documentation on [web fonts with CSS](https://fontawesome.com/how-to-use/web-fonts-with-css) for more.

themes/relearn/exampleSite/content/cont/icons.pir.md

@@ -0,0 +1,5 @@
++++
+title = "Ay'cons an' logos"
+weight = 27
++++
+{{< piratify >}}

themes/relearn/exampleSite/content/cont/markdown.en.md

@@ -0,0 +1,696 @@
++++
+title = "Markdown syntax"
+weight = 15
++++
+
+Let'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:
+
+1. Markdown is simple to learn, with minimal extra characters so it's also quicker to write content.
+2. Less chance of errors when writing in Markdown.
+3. Produces valid XHTML output.
+4. Keeps the content and the visual display separate, so you cannot mess up the look of your site.
+5. Write in any text editor or Markdown application you like.
+6. Markdown is a joy to use!
+
+John Gruber, the author of Markdown, puts it like this:
+
+> The overriding design goal for Markdown’s formatting syntax is to make it as readable as possible. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions. While Markdown’s syntax has been influenced by several existing text-to-HTML filters, the single biggest source of inspiration for Markdown’s syntax is the format of plain text email.
+> <cite>John Gruber</cite>
+
+Without further delay, let us go over the main elements of Markdown and what the resulting HTML looks like:
+
+{{% notice info %}}
+<i class="fas fa-bookmark"></i> Bookmark this page and the [official Commonmark reference](https://commonmark.org/help/) for easy future reference!
+{{% /notice %}}
+
+## Headings
+
+Headings from `h1` through `h6` are constructed with a `#` for each level:
+
+```markdown
+# h1 Heading
+## h2 Heading
+### h3 Heading
+#### h4 Heading
+##### h5 Heading
+###### h6 Heading
+```
+
+Renders to:
+<!-- markdownlint-disable MD025 -->
+# h1 Heading
+<!-- markdownlint-enable MD025 -->
+
+## h2 Heading
+
+### h3 Heading
+
+#### h4 Heading
+
+##### h5 Heading
+
+###### h6 Heading
+
+HTML:
+
+```html
+<h1>h1 Heading</h1>
+<h2>h2 Heading</h2>
+<h3>h3 Heading</h3>
+<h4>h4 Heading</h4>
+<h5>h5 Heading</h5>
+<h6>h6 Heading</h6>
+```
+
+## Comments
+
+Comments should be HTML compatible
+
+```html
+<!--
+This is a comment
+-->
+```
+
+Comment below should **NOT** be seen:
+
+<!--
+This is a comment
+-->
+
+## Horizontal Rules
+
+The HTML `<hr>` element is for creating a "thematic break" between paragraph-level elements. In Markdown, you can create a `<hr>` with `---` - three consecutive dashes
+
+renders to:
+
+---
+
+## Paragraphs
+
+Any text not starting with a special sign is written as normal, plain text and will be wrapped within `<p></p>` tags in the rendered HTML.
+
+So this body copy:
+
+```markdown
+Lorem ipsum dolor sit amet, graecis denique ei vel, at duo primis mandamus. Et legere ocurreret pri, animal tacimates complectitur ad cum. Cu eum inermis inimicus efficiendi. Labore officiis his ex, soluta officiis concludaturque ei qui, vide sensibus vim ad.
+```
+
+renders to this HTML:
+
+```html
+<p>Lorem ipsum dolor sit amet, graecis denique ei vel, at duo primis mandamus. Et legere ocurreret pri, animal tacimates complectitur ad cum. Cu eum inermis inimicus efficiendi. Labore officiis his ex, soluta officiis concludaturque ei qui, vide sensibus vim ad.</p>
+```
+
+## Text Markers
+
+### Bold
+
+For emphasizing a snippet of text with a heavier font-weight.
+
+The following snippet of text is **rendered as bold text**.
+
+```markdown
+**rendered as bold text**
+```
+
+renders to:
+
+<!-- markdownlint-disable MD036 -->
+**rendered as bold text**
+<!-- markdownlint-enable MD036 -->
+
+and this HTML
+
+```html
+<strong>rendered as bold text</strong>
+```
+
+### Italics
+
+For emphasizing a snippet of text with italics.
+
+The following snippet of text is _rendered as italicized text_.
+
+```markdown
+_rendered as italicized text_
+```
+
+renders to:
+
+<!-- markdownlint-disable MD036 -->
+_rendered as italicized text_
+<!-- markdownlint-enable MD036 -->
+
+and this HTML:
+
+```html
+<em>rendered as italicized text</em>
+```
+
+### Strikethrough
+
+In GFM (GitHub flavored Markdown) you can do strikethroughs.
+
+```markdown
+~~Strike through this text.~~
+```
+
+Which renders to:
+
+~~Strike through this text.~~
+
+HTML:
+
+```html
+<del>Strike through this text.</del>
+```
+
+## Blockquotes
+
+For quoting blocks of content from another source within your document.
+
+Add `>` before any text you want to quote.
+
+```markdown
+> **Fusion Drive** combines a hard drive with a flash storage (solid-state drive) and presents it as a single logical volume with the space of both drives combined.
+```
+
+Renders to:
+
+> **Fusion Drive** combines a hard drive with a flash storage (solid-state drive) and presents it as a single logical volume with the space of both drives combined.
+
+and this HTML:
+
+```html
+<blockquote>
+  <p><strong>Fusion Drive</strong> combines a hard drive with a flash storage (solid-state drive) and presents it as a single logical volume with the space of both drives combined.</p>
+</blockquote>
+```
+
+Blockquotes can also be nested:
+
+```markdown
+> Donec massa lacus, ultricies a ullamcorper in, fermentum sed augue. Nunc augue augue, aliquam non hendrerit ac, commodo vel nisi.
+>
+> > Sed adipiscing elit vitae augue consectetur a gravida nunc vehicula. Donec auctor odio non est accumsan facilisis. Aliquam id turpis in dolor tincidunt mollis ac eu diam.
+>
+> Mauris sit amet ligula egestas, feugiat metus tincidunt, luctus libero. Donec congue finibus tempor. Vestibulum aliquet sollicitudin erat, ut aliquet purus posuere luctus.
+```
+
+Renders to:
+
+> Donec massa lacus, ultricies a ullamcorper in, fermentum sed augue. Nunc augue augue, aliquam non hendrerit ac, commodo vel nisi.
+>
+> > Sed adipiscing elit vitae augue consectetur a gravida nunc vehicula. Donec auctor odio non est accumsan facilisis. Aliquam id turpis in dolor tincidunt mollis ac eu diam.
+>
+> Mauris sit amet ligula egestas, feugiat metus tincidunt, luctus libero. Donec congue finibus tempor. Vestibulum aliquet sollicitudin erat, ut aliquet purus posuere luctus.
+
+## Lists
+
+### Unordered
+
+A list of items in which the order of the items does not explicitly matter.
+
+You may use any of the following symbols to denote bullets for each list item:
+
+```markdown
+* valid bullet
+- valid bullet
++ valid bullet
+```
+
+For example
+
+```markdown
++ Lorem ipsum dolor sit amet
++ Consectetur adipiscing elit
++ Integer molestie lorem at massa
++ Facilisis in pretium nisl aliquet
++ Nulla volutpat aliquam velit
+  - Phasellus iaculis neque
+  - Purus sodales ultricies
+  - Vestibulum laoreet porttitor sem
+  - Ac tristique libero volutpat at
++ Faucibus porta lacus fringilla vel
++ Aenean sit amet erat nunc
++ Eget porttitor lorem
+```
+
+Renders to:
+
+<!-- markdownlint-disable MD004 -->
++ Lorem ipsum dolor sit amet
++ Consectetur adipiscing elit
++ Integer molestie lorem at massa
++ Facilisis in pretium nisl aliquet
++ Nulla volutpat aliquam velit
+  - Phasellus iaculis neque
+  - Purus sodales ultricies
+  - Vestibulum laoreet porttitor sem
+  - Ac tristique libero volutpat at
++ Faucibus porta lacus fringilla vel
++ Aenean sit amet erat nunc
++ Eget porttitor lorem
+<!-- markdownlint-enable MD004 -->
+
+And this HTML
+
+```html
+<ul>
+  <li>Lorem ipsum dolor sit amet</li>
+  <li>Consectetur adipiscing elit</li>
+  <li>Integer molestie lorem at massa</li>
+  <li>Facilisis in pretium nisl aliquet</li>
+  <li>Nulla volutpat aliquam velit
+    <ul>
+      <li>Phasellus iaculis neque</li>
+      <li>Purus sodales ultricies</li>
+      <li>Vestibulum laoreet porttitor sem</li>
+      <li>Ac tristique libero volutpat at</li>
+    </ul>
+  </li>
+  <li>Faucibus porta lacus fringilla vel</li>
+  <li>Aenean sit amet erat nunc</li>
+  <li>Eget porttitor lorem</li>
+</ul>
+```
+
+### Ordered
+
+A list of items in which the order of items does explicitly matter.
+
+```markdown
+1. Lorem ipsum dolor sit amet
+4. Consectetur adipiscing elit
+2. Integer molestie lorem at massa
+8. Facilisis in pretium nisl aliquet
+4. Nulla volutpat aliquam velit
+99. Faucibus porta lacus fringilla vel
+21. Aenean sit amet erat nunc
+6. Eget porttitor lorem
+```
+
+Renders to:
+
+1. Lorem ipsum dolor sit amet
+2. Consectetur adipiscing elit
+3. Integer molestie lorem at massa
+4. Facilisis in pretium nisl aliquet
+5. Nulla volutpat aliquam velit
+6. Faucibus porta lacus fringilla vel
+7. Aenean sit amet erat nunc
+8. Eget porttitor lorem
+
+And this HTML:
+
+```html
+<ol>
+  <li>Lorem ipsum dolor sit amet</li>
+  <li>Consectetur adipiscing elit</li>
+  <li>Integer molestie lorem at massa</li>
+  <li>Facilisis in pretium nisl aliquet</li>
+  <li>Nulla volutpat aliquam velit</li>
+  <li>Faucibus porta lacus fringilla vel</li>
+  <li>Aenean sit amet erat nunc</li>
+  <li>Eget porttitor lorem</li>
+</ol>
+```
+
+{{% notice tip %}}
+If you just use `1.` for each number, Markdown will automatically number each item. For example:
+{{% /notice %}}
+
+```markdown
+1. Lorem ipsum dolor sit amet
+1. Consectetur adipiscing elit
+1. Integer molestie lorem at massa
+1. Facilisis in pretium nisl aliquet
+1. Nulla volutpat aliquam velit
+1. Faucibus porta lacus fringilla vel
+1. Aenean sit amet erat nunc
+1. Eget porttitor lorem
+```
+
+Renders to:
+
+1. Lorem ipsum dolor sit amet
+2. Consectetur adipiscing elit
+3. Integer molestie lorem at massa
+4. Facilisis in pretium nisl aliquet
+5. Nulla volutpat aliquam velit
+6. Faucibus porta lacus fringilla vel
+7. Aenean sit amet erat nunc
+8. Eget porttitor lorem
+
+## Code
+
+### Inline code
+
+Wrap inline snippets of code with `` ` ``.
+
+```markdown
+In this example, `<div></div>` should be wrapped as **code**.
+```
+
+Renders to:
+
+In this example, `<div></div>` should be wrapped as **code**.
+
+HTML:
+
+```html
+<p>In this example, <code>&lt;div&gt;&lt;/div&gt;</code> should be wrapped as <strong>code</strong>.</p>
+```
+
+### Indented code
+
+Or indent several lines of code by at least two spaces, as in:
+
+```markdown
+    // Some comments
+    line 1 of code
+    line 2 of code
+    line 3 of code
+```
+
+Renders to:
+
+<!-- markdownlint-disable MD046 -->
+    // Some comments
+    line 1 of code
+    line 2 of code
+    line 3 of code
+<!-- markdownlint-enable MD046 -->
+
+HTML:
+
+```html
+<pre>
+  <code>
+    // Some comments
+    line 1 of code
+    line 2 of code
+    line 3 of code
+  </code>
+</pre>
+```
+
+### Block code "fences"
+
+Use "fences"  ```` ``` ```` to block in multiple lines of code.
+
+````plaintext
+```
+Sample text here...
+```
+````
+
+HTML:
+
+```html
+<pre>
+  <code>Sample text here...</code>
+</pre>
+```
+
+### Syntax highlighting
+
+GFM, or "GitHub Flavored Markdown" also supports syntax highlighting. To activate it, usually you simply add the file extension of the language you want to use directly after the first code "fence", ` ```js `, and syntax highlighting will automatically be applied in the rendered HTML.
+
+See [Code Highlighting]({{% relref "syntaxhighlight" %}}) for additional documentation.
+
+For example, to apply syntax highlighting to JavaScript code:
+
+````plaintext
+```js
+grunt.initConfig({
+  assemble: {
+    options: {
+      assets: 'docs/assets',
+      data: 'src/data/*.{json,yml}',
+      helpers: 'src/custom-helpers.js',
+      partials: ['src/partials/**/*.{hbs,md}']
+    },
+    pages: {
+      options: {
+        layout: 'default.hbs'
+      },
+      files: {
+        './': ['src/templates/pages/index.hbs']
+      }
+    }
+  }
+};
+```
+````
+
+Renders to:
+
+```js
+grunt.initConfig({
+  assemble: {
+    options: {
+      assets: 'docs/assets',
+      data: 'src/data/*.{json,yml}',
+      helpers: 'src/custom-helpers.js',
+      partials: ['src/partials/**/*.{hbs,md}']
+    },
+    pages: {
+      options: {
+        layout: 'default.hbs'
+      },
+      files: {
+        './': ['src/templates/pages/index.hbs']
+      }
+    }
+  }
+};
+```
+
+## Tables
+
+Tables are created by adding pipes as dividers between each cell, and by adding a line of dashes (also separated by bars) beneath the header. Note that the pipes do not need to be vertically aligned.
+
+```markdown
+| Option | Description |
+| ------ | ----------- |
+| data   | path to data files to supply the data that will be passed into templates. |
+| engine | engine to be used for processing templates. Handlebars is the default. |
+| ext    | extension to be used for dest files. |
+```
+
+Renders to:
+
+| Option | Description |
+| ------ | ----------- |
+| data   | path to data files to supply the data that will be passed into templates. |
+| engine | engine to be used for processing templates. Handlebars is the default. |
+| ext    | extension to be used for dest files. |
+
+And this HTML:
+
+```html
+<table>
+  <tr>
+    <th>Option</th>
+    <th>Description</th>
+  </tr>
+  <tr>
+    <td>data</td>
+    <td>path to data files to supply the data that will be passed into templates.</td>
+  </tr>
+  <tr>
+    <td>engine</td>
+    <td>engine to be used for processing templates. Handlebars is the default.</td>
+  </tr>
+  <tr>
+    <td>ext</td>
+    <td>extension to be used for dest files.</td>
+  </tr>
+</table>
+```
+
+### Right aligned text
+
+Adding a colon on the right side of the dashes below any heading will right align text for that column.
+
+```markdown
+| Option | Description |
+| ------:| -----------:|
+| data   | path to data files to supply the data that will be passed into templates. |
+| engine | engine to be used for processing templates. Handlebars is the default. |
+| ext    | extension to be used for dest files. |
+```
+
+| Option | Description |
+| ------:| -----------:|
+| data   | path to data files to supply the data that will be passed into templates. |
+| engine | engine to be used for processing templates. Handlebars is the default. |
+| ext    | extension to be used for dest files. |
+
+### Two tables adjacent
+
+| Option | Description |
+| ------ | ----------- |
+| ext    | extension to be used for dest files. |
+
+| Option | Description |
+| ------ | ----------- |
+| ext    | extension to be used for dest files. |
+
+## Links
+
+### Basic link
+
+```markdown
+[Assemble](http://assemble.io)
+```
+
+Renders to (hover over the link, there is no tooltip):
+
+[Assemble](http://assemble.io)
+
+HTML:
+
+```html
+<a href="http://assemble.io">Assemble</a>
+```
+
+### Add a tooltip
+
+```markdown
+[Upstage](https://github.com/upstage/ "Visit Upstage!")
+```
+
+Renders to (hover over the link, there should be a tooltip):
+
+[Upstage](https://github.com/upstage/ "Visit Upstage!")
+
+HTML:
+
+```html
+<a href="https://github.com/upstage/" title="Visit Upstage!">Upstage</a>
+```
+
+### Named Anchors
+
+Named anchors enable you to jump to the specified anchor point on the same page. For example, each of these chapters:
+
+```markdown
+# Table of Contents
+  * [Chapter 1](#chapter-1)
+  * [Chapter 2](#chapter-2)
+  * [Chapter 3](#chapter-3)
+```
+
+will jump to these sections:
+
+```markdown
+## Chapter 1 <a id="chapter-1"></a>
+Content for chapter one.
+
+## Chapter 2 <a id="chapter-2"></a>
+Content for chapter one.
+
+## Chapter 3 <a id="chapter-3"></a>
+Content for chapter one.
+```
+**NOTE** that specific placement of the anchor tag seems to be arbitrary. They are placed inline here since it seems to be unobtrusive, and it works.
+
+## Images {#images}
+Images have a similar syntax to links but include a preceding exclamation point.
+
+```markdown
+![Minion](https://octodex.github.com/images/minion.png)
+```
+
+![Minion](https://octodex.github.com/images/minion.png)
+
+or
+
+```markdown
+![Alt text](https://octodex.github.com/images/stormtroopocat.jpg "The Stormtroopocat")
+```
+
+![Alt text](https://octodex.github.com/images/stormtroopocat.jpg "The Stormtroopocat")
+
+Like links, Images also have a footnote style syntax
+
+### Alternative usage : note images
+
+```markdown
+![Alt text][id]
+```
+
+![Alt text][id]
+
+With a reference later in the document defining the URL location:
+
+[id]: https://octodex.github.com/images/dojocat.jpg  "The Dojocat"
+
+    [id]: https://octodex.github.com/images/dojocat.jpg  "The Dojocat"
+
+### Further image formatting
+
+The Hugo Markdown parser supports additional non-standard functionality.
+
+#### Resizing image
+
+Add HTTP parameters `width` and/or `height` to the link image to resize the image. Values are CSS values (default is `auto`).
+
+```markdown
+![Minion](https://octodex.github.com/images/minion.png?width=20pc)
+```
+
+![Minion](https://octodex.github.com/images/minion.png?width=20pc)
+
+![stormtroopocat](https://octodex.github.com/images/stormtroopocat.png?width=20pc)
+
+```markdown
+![Minion](https://octodex.github.com/images/minion.png?height=50px)
+```
+
+![Minion](https://octodex.github.com/images/minion.png?height=50px)
+
+```markdown
+![Minion](https://octodex.github.com/images/minion.png?height=50px&width=300px)
+```
+
+![Minion](https://octodex.github.com/images/minion.png?height=50px&width=300px)
+
+#### Add CSS classes
+
+Add a HTTP `classes` parameter to the link image to add CSS classes. `shadow`and `border` are available but you could define other ones.
+
+```markdown
+![stormtroopocat](https://octodex.github.com/images/stormtroopocat.jpg?classes=shadow)
+```
+
+![stormtroopocat](https://octodex.github.com/images/stormtroopocat.jpg?width=40pc&classes=shadow)
+
+```markdown
+![stormtroopocat](https://octodex.github.com/images/stormtroopocat.jpg?classes=border)
+```
+
+![stormtroopocat](https://octodex.github.com/images/stormtroopocat.jpg?width=40pc&classes=border)
+
+```markdown
+![stormtroopocat](https://octodex.github.com/images/stormtroopocat.jpg?classes=border,shadow)
+```
+
+![stormtroopocat](https://octodex.github.com/images/stormtroopocat.jpg?width=40pc&classes=border,shadow)
+
+#### Lightbox
+
+Add a HTTP `featherlight` parameter to the link image to disable lightbox. By default lightbox is enabled using the featherlight.js plugin. You can disable this by defining `featherlight` to `false`.
+
+```markdown
+![Minion](https://octodex.github.com/images/minion.png?featherlight=false)
+```
+
+![Minion](https://octodex.github.com/images/minion.png?featherlight=false)

themes/relearn/exampleSite/content/cont/markdown.pir.md

@@ -0,0 +1,5 @@
++++
+title = "Marrrkdown rules"
+weight = 15
++++
+{{< piratify >}}

themes/relearn/exampleSite/content/cont/menushortcuts.en.md

@@ -0,0 +1,132 @@
++++
+title = "Menu extra shortcuts"
+weight = 25
++++
+
+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:
+
+````toml
+[[menu.shortcuts]]
+name = "<i class='fab fa-fw fa-github'></i> GitHub repo"
+identifier = "ds"
+url = "https://github.com/McShelby/hugo-theme-relearn"
+weight = 10
+
+[[menu.shortcuts]]
+name = "<i class='fas fa-fw fa-camera'></i> Showcases"
+url = "more/showcase/"
+weight = 11
+
+[[menu.shortcuts]]
+name = "<i class='fas fa-fw fa-bookmark'></i> Hugo Documentation"
+identifier = "hugodoc"
+url = "https://gohugo.io/"
+weight = 20
+
+[[menu.shortcuts]]
+name = "<i class='fas fa-fw fa-bullhorn'></i> Credits"
+url = "more/credits/"
+weight = 30
+
+[[menu.shortcuts]]
+name = "<i class='fas fa-fw fa-tags'></i> Tags"
+url = "tags/"
+weight = 40
+````
+
+By default, shortcuts are preceded by a title. This title can be disabled by setting `disableShortcutsTitle=true`.
+However, if you want to keep the title but change its value, it can be overriden by changing your local i18n translation string configuration.
+
+For example, in your local `i18n/en.toml` file, add the following content
+
+````toml
+[Shortcuts-Title]
+other = "<Your value>"
+````
+
+Read more about [hugo menu](https://gohugo.io/extras/menus/) and [hugo i18n translation strings](https://gohugo.io/content-management/multilingual/#translation-of-strings)
+
+## Configuration for Multilingual mode {#i18n}
+
+When using a multilingual website, you can set different menus for each language. In the `config.toml` file, prefix your menu configuration by `Languages.<language-id>`.
+
+Example from the current website:
+
+````toml
+[Languages]
+  [Languages.en]
+    title = "Hugo Relearn Theme"
+    weight = 1
+    languageName = "English"
+    landingPageURL = "/"
+    landingPageName = "<i class='fas fa-home'></i> Home"
+
+  [[Languages.en.menu.shortcuts]]
+    name = "<i class='fab fa-fw fa-github'></i> GitHub repo"
+    identifier = "ds"
+    url = "https://github.com/McShelby/hugo-theme-relearn"
+    weight = 10
+
+  [[Languages.en.menu.shortcuts]]
+    name = "<i class='fas fa-fw fa-camera'></i> Showcases"
+    url = "more/showcase/"
+    weight = 11
+
+  [[Languages.en.menu.shortcuts]]
+    name = "<i class='fas fa-fw fa-bookmark'></i> Hugo Documentation"
+    identifier = "hugodoc"
+    url = "https://gohugo.io/"
+    weight = 20
+
+  [[Languages.en.menu.shortcuts]]
+    name = "<i class='fas fa-fw fa-bullhorn'></i> Credits"
+    url = "more/credits/"
+    weight = 30
+
+  [[Languages.en.menu.shortcuts]]
+    name = "<i class='fas fa-fw fa-tags'></i> Tags"
+    url = "tags/"
+    weight = 40
+
+  [Languages.pir]
+    title = "Cap'n Hugo Relearrrn Theme"
+    weight = 1
+    languageName = "Arrr! Pirrrates"
+    landingPageURL = "/pir/"
+    landingPageName = "<i class='fas fa-home'></i> Arrr! Home"
+
+  [[Languages.pir.menu.shortcuts]]
+    name = "<i class='fab fa-fw fa-github'></i> GitHub repo"
+    identifier = "ds"
+    url = "https://github.com/McShelby/hugo-theme-relearn"
+    weight = 10
+
+  [[Languages.pir.menu.shortcuts]]
+    name = "<i class='fas fa-fw fa-camera'></i> Showcases"
+    url = "more/showcase/"
+    weight = 11
+
+  [[Languages.pir.menu.shortcuts]]
+    name = "<i class='fas fa-fw fa-bookmark'></i> Cap'n Hugo Documentat'n"
+    identifier = "hugodoc"
+    url = "https://gohugo.io/"
+    weight = 20
+
+  [[Languages.pir.menu.shortcuts]]
+    name = "<i class='fas fa-fw fa-bullhorn'></i> Crrredits"
+    url = "more/credits/"
+    weight = 30
+
+  [[Languages.pir.menu.shortcuts]]
+    name = "<i class='fas fa-fw fa-tags'></i> Arrr! Tags"
+    url = "tags/"
+    weight = 40
+````
+
+Read more about [hugo menu](https://gohugo.io/extras/menus/) and [hugo multilingual menus](https://gohugo.io/content-management/multilingual/#menus)

themes/relearn/exampleSite/content/cont/menushortcuts.pir.md

@@ -0,0 +1,5 @@
++++
+title = "Menu extrrra shorrrtcuts"
+weight = 25
++++
+{{< piratify >}}

themes/relearn/exampleSite/content/cont/pages/_index.en.md

@@ -0,0 +1,191 @@
++++
+title = "Pages organization"
+weight = 5
++++
+
+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](https://gohugo.io/content/organization/). Typically, you will have a *content* folder with all your pages.
+
+````plaintext
+content
+├── level-one
+│   ├── level-two
+│   │   ├── level-three
+│   │   │   ├── level-four
+│   │   │   │   ├── _index.md       <-- /level-one/level-two/level-three/level-four
+│   │   │   │   ├── page-4-a.md     <-- /level-one/level-two/level-three/level-four/page-4-a
+│   │   │   │   ├── page-4-b.md     <-- /level-one/level-two/level-three/level-four/page-4-b
+│   │   │   │   └── page-4-c.md     <-- /level-one/level-two/level-three/level-four/page-4-c
+│   │   │   ├── _index.md           <-- /level-one/level-two/level-three
+│   │   │   ├── page-3-a.md         <-- /level-one/level-two/level-three/page-3-a
+│   │   │   ├── page-3-b.md         <-- /level-one/level-two/level-three/page-3-b
+│   │   │   └── page-3-c.md         <-- /level-one/level-two/level-three/page-3-c
+│   │   ├── _index.md               <-- /level-one/level-two
+│   │   ├── page-2-a.md             <-- /level-one/level-two/page-2-a
+│   │   ├── page-2-b.md             <-- /level-one/level-two/page-2-b
+│   │   └── page-2-c.md             <-- /level-one/level-two/page-2-c
+│   ├── _index.md                   <-- /level-one
+│   ├── page-1-a.md                 <-- /level-one/page-1-a
+│   ├── page-1-b.md                 <-- /level-one/page-1-b
+│   └── page-1-c.md                 <-- /level-one/page-1-c
+├── _index.md                       <-- /
+└── page-top.md                     <-- /page-top
+````
+
+{{% notice note %}}
+`_index.md` is required in each folder, it’s your “folder home page”
+{{% /notice %}}
+
+## Types
+
+The Relearn theme defines two types of pages. *Default* and *Chapter*. Both can be used at any level of the documentation, the only difference being layout display.
+
+### Chapter {#chapter-style}
+
+A **Chapter** displays a page meant to be used as introduction for a set of child pages. Commonly, it contains a simple title and a catch line to define content that can be found under it.
+
+You can define any HTML as prefix for the menu. In the example below, it's just a number but that could be an [icon](https://fortawesome.github.io/Font-Awesome/).
+
+![Chapter page](images/pages-chapter.png?classes=shadow&width=60pc)
+
+```markdown
++++
+chapter = true
+pre = "<b>1. </b>"
+title = "Basics"
+weight = 5
++++
+
+### Chapter 1
+
+# Basics
+
+Discover what this Hugo theme is all about and the core-concepts behind it.
+```
+
+To tell the Relearn theme to consider a page as a chapter, set `chapter=true` in the Front Matter of the page.
+
+### Default
+
+A **Default** page is any other content page.
+
+![Default page](images/pages-default.png?classes=shadow&width=60pc)
+
+```toml
++++
+title = "Installation"
+weight = 15
++++
+```
+
+The following steps are here to help you initialize your new website. If you don't know Hugo at all, we strongly suggest you to train by following this [great documentation for beginners](https://gohugo.io/overview/quickstart/).
+
+## Create your project
+
+Hugo provides a `new` command to create a new website.
+
+```shell
+hugo new site <new_project>
+```
+
+The Relearn theme provides [archetypes]({{%relref "cont/archetypes" %}}) to help you create this kind of pages.
+
+## Front Matter configuration
+
+Each Hugo page has to define a [Front Matter](https://gohugo.io/content/front-matter/) in *toml*, *yaml* or *json*. This site will use *toml* in all cases.
+
+The Relearn theme uses the following parameters on top of Hugo ones :
+
+```toml
++++
+# Table of contents (toc) is enabled by default. Set this parameter to true to disable it.
+# Note: Toc is always disabled for chapter pages
+disableToc = false
+# If set, this will be used for the page's menu entry (instead of the `title` attribute)
+menuTitle = ""
+# If set, this will explicitly override common rules for the expand state of a page's menu entry
+alwaysopen = true
+# If set, this will explicitly override common rules for the sorting order of a page's submenu entries
+ordersectionsby = "title"
+# The title of the page in menu will be prefixed by this HTML content
+pre = ""
+# The title of the page in menu will be postfixed by this HTML content
+post = ""
+# Set the page as a chapter, changing the way it's displayed
+chapter = false
+# Hide a menu entry by setting this to true
+hidden = false
+# Display name of this page modifier. If set, it will be displayed in the footer.
+LastModifierDisplayName = ""
+# Email of this page modifier. If set with LastModifierDisplayName, it will be displayed in the footer
+LastModifierEmail = ""
++++
+```
+
+### Add icon to a menu entry
+
+In the page frontmatter, add a `pre` param to insert any HTML code before the menu label. The example below uses the GitHub icon.
+
+```toml
++++
+title = "GitHub repo"
+pre = "<i class='fab fa-github'></i> "
++++
+```
+
+![Title with icon](images/frontmatter-icon.png?classes=shadow&width=300px)
+
+### Ordering sibling menu/page entries
+
+Hugo provides a [flexible way](https://gohugo.io/content/ordering/) to handle order for your pages.
+
+The simplest way is to set `weight` parameter to a number.
+
+```toml
++++
+title = "My page"
+weight = 5
++++
+```
+
+### Using a custom title for menu entries
+
+By default, the Relearn theme will use a page's `title` attribute for the menu item (or `linkTitle` if defined).
+
+But a page's title has to be descriptive on its own while the menu is a hierarchy.
+We've added the `menuTitle` parameter for that purpose:
+
+For example (for a page named `content/install/linux.md`):
+
+```toml
++++
+title = "Install on Linux"
+menuTitle = "Linux"
++++
+```
+
+### Override expand state rules for menu entries
+
+You can change how the theme expands menu entries on the side of the content with the `alwaysopen` setting on a per page basis. If `alwaysopen=false` for any given entry, its children will not be shown in the menu as long as it is not necessary for the sake of navigation.
+
+The theme generates the menu based on the following rules:
+
+- all parent entries of the active page including their siblings are shown regardless of any settings
+- immediate children entries of the active page are shown regardless of any settings
+- if not overridden, all other first level entries behave like they would have been given `alwaysopen=false`
+- if not overridden, all other entries of levels besides the first behave like they would have been given `alwaysopen=true`
+- all visible entries show their immediate children entries if `alwaysopen=true`; this proceeds recursivley
+- all remaining entries are not shown
+
+You can see this feature in action on the example page for [children shortcode]({{< relref "shortcodes/children" >}}) and its children pages.
+
+## Your Page
+
+To configure your page, you basically have three choices:
+
+1. Create an `_index.md` document in `content` folder and fill the file with *Markdown content*
+2. Create an `index.html` file in the `static` folder and fill the file with *HTML content*
+3. Configure your server to automatically redirect home page to one your documentation page

themes/relearn/exampleSite/content/cont/pages/_index.pir.md

@@ -0,0 +1,5 @@
++++
+title = "Planks orrrganizat'n"
+weight = 5
++++
+{{< piratify >}}

themes/relearn/exampleSite/content/cont/syntaxhighlight.en.md

@@ -0,0 +1,66 @@
++++
+title = "Code highlighting"
+weight = 16
++++
+
+The Relearn theme uses [Hugo's built-in syntax highlighting](https://gohugo.io/content-management/syntax-highlighting/) for code.
+
+## Markdown syntax
+
+Wrap the code block with three backticks and the name of the language. Highlight will try to auto detect the language if one is not provided.
+
+<!-- markdownlint-disable MD046 -->
+````plaintext
+```json
+[
+  {
+    "title": "apples",
+    "count": [12000, 20000],
+    "description": {"text": "...", "sensitive": false}
+  },
+  {
+    "title": "oranges",
+    "count": [17500, null],
+    "description": {"text": "...", "sensitive": false}
+  }
+]
+```
+````
+<!-- markdownlint-disable MD046 -->
+
+Renders to:
+
+```json
+[
+  {
+    "title": "apples",
+    "count": [12000, 20000],
+    "description": {"text": "...", "sensitive": false}
+  },
+  {
+    "title": "oranges",
+    "count": [17500, null],
+    "description": {"text": "...", "sensitive": false}
+  }
+]
+```
+
+## Supported languages
+
+Hugo comes with a [remarkable list](https://gohugo.io/content-management/syntax-highlighting/#list-of-chroma-highlighting-languages) of supported languages.
+
+## Recommended configuration
+
+You can choose a color theme from the [list of supported themes](https://xyproto.github.io/splash/docs/all.html) and add it in your `config.toml`
+
+````toml
+[markup]
+  [markup.highlight]
+    # if set to `guessSyntax = true`, there will be no unstyled code even if no language
+    # was given BUT mermaid code fences will not work anymore! So this is a mandatory
+    # setting for your site
+    guessSyntax = false
+
+    # choose a color theme or create your own
+    style = "base16-snazzy"
+````

themes/relearn/exampleSite/content/cont/syntaxhighlight.pir.md

@@ -0,0 +1,5 @@
++++
+title = "Code highlight'n"
+weight = 16
++++
+{{< piratify >}}

themes/relearn/exampleSite/content/cont/tags.en.md

@@ -0,0 +1,36 @@
++++
+tags = ["documentation", "tutorial"]
+title = "Tags"
+weight = 40
++++
+
+The Relearn theme supports one default taxonomy of Hugo: the *tag* feature.
+
+## Configuration
+
+Just add tags to any page:
+
+```toml
++++
+tags = ["tutorial", "theme"]
+title = "Theme tutorial"
+weight = 15
++++
+```
+
+## Behavior
+
+The tags are displayed at the top of the page, in their insertion order.
+
+Each tag is a link to a *Taxonomy* page displaying all the articles with the given tag.
+
+## List all the tags
+
+In the `config.toml`  file you can add a shortcut to display all the tags
+
+```toml
+[[menu.shortcuts]]
+name = "<i class='fas fa-tags'></i> Tags"
+url = "/tags"
+weight = 30
+```

themes/relearn/exampleSite/content/cont/tags.pir.md

@@ -0,0 +1,6 @@
++++
+tags = ["documentat'n", "tutorrrial"]
+title = "Tags"
+weight = 40
++++
+{{< piratify >}}