rbcli 0.2.11 → 0.2.12

data/docs-src/themes/hugo-theme-learn/exampleSite/content/cont/_index.en.md

@@ -0,0 +1,12 @@
+---
+title: Content
+weight: 10
+chapter: true
+pre: "<b>2. </b>"
+---
+
+### Chapter 2
+
+# Content
+
+Find out how to create and organize your content quickly and intuitively.

data/docs-src/themes/hugo-theme-learn/exampleSite/content/cont/_index.fr.md

@@ -0,0 +1,12 @@
+---
+title: Contenu
+weight: 10
+chapter: true
+pre: "<b>2. </b>"
+---
+
+### Chapitre 2
+
+# Contenu
+
+Découvrez comment créer et organiser votre contenu facilement et intuitivement.

data/docs-src/themes/hugo-theme-learn/exampleSite/content/cont/archetypes.en.md

@@ -0,0 +1,57 @@
+---
+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
+
+```
+hugo new --kind chapter <name>/_index.md
+```
+
+It will create a page with predefined Front-Matter:
+
+```markdown
++++
+title = "{{ replace .Name "-" " " | title }}"
+date = {{ .Date }}
+weight = 5
+chapter = true
+pre = "<b>X. </b>"
++++
+
+### Chapter X
+
+# Some Chapter title
+
+Lorem Ipsum.
+```
+
+## Default
+
+To create a default page, run either one of the following commands
+
+```
+# Either
+hugo new <chapter>/<name>/_index.md
+# Or
+hugo new <chapter>/<name>.md
+```
+
+It will create a page with predefined Front-Matter:
+
+```markdown
++++
+title = "{{ replace .Name "-" " " | title }}"
+date =  {{ .Date }}
+weight = 5
++++
+
+Lorem Ipsum.
+```

data/docs-src/themes/hugo-theme-learn/exampleSite/content/cont/archetypes.fr.md

@@ -0,0 +1,57 @@
+---
+title: Archétypes
+weight: 10
+---
+
+En utilisant la commande: `hugo new [chemin vers nouveau contenu]`, vous pouvez créer un nouveau fichier avec la date et le title automatiquement initialisé. Même si c'est une fonctionnalité intéressante, elle reste limitée pour les auteurs actifs qui ont besoin de mieux : les [archetypes](https://gohugo.io/content/archetypes/).
+
+Les archétypes sont des squelettes de pages préconfigurées avec un Front Matter par défaut. Merci de vous référer à la documentation pour connaitre les différents types de page.
+
+## Chapitre {#archetypes-chapter}
+
+Pour créer un chapitre, lancez les commandes suivantes
+
+```
+hugo new --kind chapter <name>/_index.md
+```
+
+Cela crééra une page avec le Front Matter suivant:
+
+```markdown
++++
+title = "{{ replace .Name "-" " " | title }}"
+date = {{ .Date }}
+weight = 5
+chapter = true
+pre = "<b>X. </b>"
++++
+
+### Chapter X
+
+# Some Chapter title
+
+Lorem Ipsum.
+```
+
+## Défaut
+
+Pour créer une page classique, lancer l'une des deux commandes suivantes
+
+```
+# Soit
+hugo new <chapter>/<name>/_index.md
+# Ou
+hugo new <chapter>/<name>.md
+```
+
+Cela crééra une page avec le Front Matter suivant:
+
+```markdown
++++
+title = "{{ replace .Name "-" " " | title }}"
+date =  {{ .Date }}
+weight = 5
++++
+
+Lorem Ipsum.
+```

data/docs-src/themes/hugo-theme-learn/exampleSite/content/cont/i18n/_index.en.md

@@ -0,0 +1,78 @@
+---
+date: 2016-04-09T16:50:16+02:00
+title: Multilingual and i18n
+weight: 30
+---
+
+**Learn theme** is fully compatible with Hugo multilingual mode.
+
+It provides:
+
+- Translation strings for default values (English and French). Feel free to contribute !
+- Automatic menu generation from multilingual content
+- In-browser language switching
+
+![I18n menu](/en/cont/i18n/images/i18n-menu.gif)
+
+## 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 French and English website.
+
+```toml
+# English is the default language
+defaultContentLanguage = "en"
+# Force to have /en/my-page and /fr/my-page routes, even for default language.
+defaultContentLanguageInSubdir= true
+
+[Languages]
+[Languages.en]
+title = "Documentation for Hugo Learn Theme"
+weight = 1
+languageName = "English"
+
+[Languages.fr]
+title = "Documentation du thème Hugo Learn"
+weight = 2
+languageName = "Français"
+```
+
+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.en.md`
+    - in French: `my-page.fr.md`
+- Single file `_index.md` is split in two files:
+    - in English: `_index.en.md`
+    - in French: `_index.fr.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 this page* button, *Search placeholder* and so on). Translations are available in french and 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-learn/i18n/en.toml` 
+
+By the way, as these translations could be used by other people, please take the time to propose a translation by [making a PR](https://github.com/matcornic/hugo-theme-learn/pulls) to the theme ! 
+
+## 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
+```
+
+![I18n menu](/en/cont/i18n/images/i18n-menu.gif)

data/docs-src/themes/hugo-theme-learn/exampleSite/content/cont/i18n/_index.fr.md

@@ -0,0 +1,78 @@
+---
+date: 2016-04-09T16:50:16+02:00
+title: Multi-langue et i18n
+weight: 30
+---
+
+**Learn** est complètement compatible avec le mode multi-langue d'Hugo.
+
+Il fournit :
+
+- Des *translation strings* pour les valeurs par défaut utilisées par le thème (Anglais et Français). N'hésitez pas à contribuer !
+- Génération automatique du menu avec le contenu multi-langue
+- Modification de la langue dans le navigateur
+
+![I18n menu](/en/cont/i18n/images/i18n-menu.gif)
+
+## Configuration simple
+
+Après avoir appris [comment Hugo gère les sites multi-langue](https://gohugo.io/content-management/multilingual), définissez vos langues dans votre fichier `config.toml`.
+
+Par exemple, pour ce site, avec du contenu en français et en anglais.
+
+```toml
+# Anglais est la langue par défaut
+defaultContentLanguage = "en"
+# Force d'avoir /en/ma-page et /fr/ma-page routes, même avec la langue par défaut.
+defaultContentLanguageInSubdir= true
+
+[Languages]
+[Languages.en]
+title = "Documentation for Hugo Learn Theme"
+weight = 1
+languageName = "English"
+
+[Languages.fr]
+title = "Documentation du thème Hugo Learn"
+weight = 2
+languageName = "Français"
+```
+
+Puis, pour chaque nouvelle page, ajoutez *l'id* de la langue du fichier.
+
+- Le fichier `my-page.md` est découpé en deux fichiers :
+    - en anglais : `my-page.en.md`
+    - en français : `my-page.fr.md`
+- Le fichier `_index.md` est découpé en deux fichiers :
+    - en anglais: `_index.en.md`
+    - en français: `_index.fr.md`
+
+{{% notice info %}}
+Attention, seulement les pages traduites sont affichées dans le menu. Le contenu n'est pas remplacé par les pages de la langue par défaut.
+{{% /notice %}}
+
+{{% notice tip %}}
+Utilisez le paramètre du Front Matter [slug](https://gohugo.io/content-management/multilingual/#translate-your-content) pour traduire également les URLs.
+{{% /notice %}}
+
+## Surcharger les *translation strings*
+
+Les *Translations strings* sont utilisées comme valeurs par défaut dans le thème (Bouton *Modifier la page*, Element de subsitution *Recherche*, etc.). Les traductions sont disponibles en français et en anglais mais vous pouvez utiliser n'importe quelle autre langue et surcharger avec vos propres valeurs.
+
+Pour surcharger ces valeurs, créer un nouveau fichier dans votre dossier i18n local `i18n/<idlanguage>.toml` et inspirez vous du thème `themes/hugo-theme-learn/i18n/en.toml` 
+
+D'ailleurs, ces traductions pour servir à tout le monde, donc svp prenez le temps de [proposer une Pull Request](https://github.com/matcornic/hugo-theme-learn/pulls) ! 
+
+## Désactiver le changement de langue
+
+Vous pouvez changer de langue directement dans le navigateur. C'est une super fonctionnalité, mais vous avez peut-être besoin de la désactiver. 
+
+Pour ce faire, ajouter le paramètre `disableLanguageSwitchingButton=true` dans votre `config.toml`
+
+```toml
+[params]
+  # Quand vous utilisez un site en multi-langue, désactive le bouton de changment de langue.
+  disableLanguageSwitchingButton = true
+```
+
+![I18n menu](/en/cont/i18n/images/i18n-menu.gif)

data/docs-src/themes/hugo-theme-learn/exampleSite/content/cont/icons.en.md

@@ -0,0 +1,41 @@
+---
+title: Icons and logos
+weight: 27
+---
+
+The Learn 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/icons?d=gallery&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/icons/heart?style=solid), copy the HTML reference and paste into the markdown content.
+
+The HTML to include the heart icon is:
+
+```
+<i class="fas fa-heart"></i>
+```
+
+## Including in markdown
+
+Paste the `<i>` HTML into markup and Font Awesome will load the relevant icon.
+
+```
+Built with <i class="fas fa-heart"></i> from Grav and Hugo
+```
+
+Which appears as
+
+Built with <i class="fas fa-heart"></i> from Grav and Hugo
+
+## Customising icons
+
+Font Awesome provides many ways to modify the icon
+
+* Change colour (by default the icon will inherit the parent colour)
+* 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.

data/docs-src/themes/hugo-theme-learn/exampleSite/content/cont/markdown.en.md

@@ -0,0 +1,665 @@
+---
+date: 2016-04-09T16:50:16+02:00
+title: Markdown syntax
+weight: 15
+---
+
+{{% notice note %}}
+This page is a shameful copy of the great [Grav original page](http://learn.getgrav.org/content/markdown).
+Only difference is information about image customization ([resizing]({{< relref "#resizing-image" >}}), [add CSS classes]({{< relref "#add-css-classes" >}})...)
+{{% /notice%}}
+
+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>
+
+
+Grav ships with built-in support for [Markdown](http://daringfireball.net/projects/markdown/) and [Markdown Extra](https://michelf.ca/projects/php-markdown/extra/). You must enable **Markdown Extra** in your `system.yaml` configuration file
+
+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 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:
+
+# h1 Heading
+## 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 any of the following:
+
+* `___`: three consecutive underscores
+* `---`: three consecutive dashes
+* `***`: three consecutive asterisks
+
+renders to:
+
+___
+
+---
+
+***
+
+
+## Body Copy
+
+Body copy written as normal, plain text will be wrapped with `<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>
+```
+
+## Emphasis
+
+### 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:
+
+**rendered as bold text**
+
+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:
+
+_rendered as italicized text_
+
+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.
+
+## Notices
+
+{{% notice note %}}
+The old mechanism for notices overriding the block quote syntax (`>>>`) has been deprecated.  Notices are now handled via a dedicated plugin called [Markdown Notices](https://github.com/getgrav/grav-plugin-markdown-notices)
+{{% /notice %}}
+
+
+## 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:
+
++ 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
+
+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
+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
+```
+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>
+```
+
+**TIP**: If you just use `1.` for each number, Markdown will automatically number each item. For example:
+
+```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, `<section></section>` should be wrapped as **code**.
+```
+
+Renders to:
+
+In this example, `<section></section>` should be wrapped with **code**.
+
+HTML:
+
+```html
+<p>In this example, <code>&lt;section&gt;&lt;/section&gt;</code> should be wrapped with <strong>code</strong>.</p>
+```
+
+### Indented code
+
+Or indent several lines of code by at least four spaces, as in:
+
+<pre>
+  // Some comments
+  line 1 of code
+  line 2 of code
+  line 3 of code
+</pre>
+
+Renders to:
+
+    // Some comments
+    line 1 of code
+    line 2 of code
+    line 3 of code
+
+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.
+
+<pre>
+``` markup
+Sample text here...
+```
+</pre>
+
+
+```
+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, 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. For example, to apply syntax highlighting to JavaScript code:
+
+<pre>
+```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']
+      }
+    }
+  }
+};
+```
+</pre>
+
+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. |
+
+## 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 title
+
+```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"
+
+### 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)
+
+```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)