<!--more--> summary divider where you want to split the article. Content that comes before the summary divider will be used as that content's summary and stored in the `.Summary` page variable with all HTML formatting intact.
+Alternatively, you may add the <!--more--> summary divider where you want to split the article. For [org content][org], use # more) where you want to split the article. Content that comes before the summary divider will be used as that content's summary and stored in the `.Summary` page variable with all HTML formatting intact.
{{% note "Summary Divider"%}}
The concept of a *summary divider* is not unique to Hugo. It is also called the "more tag" or "excerpt separator" in other literature.
{{% /note %}}
* Pros: Freedom, precision, and improved rendering. All HTML tags and formatting are preserved.
-* Cons: Extra work for content authors, since they need to remember to type <!--more--> in each content file.
+* Cons: Extra work for content authors, since they need to remember to type <!--more--> (or `# more` for [org content][org]) in each content file.
{{% warning "Be Precise with the Summary Divider" %}}
Be careful to enter <!--more--> exactly; i.e., all lowercase and with no whitespace. Any mistakes in the divider will tell Hugo to treat the divider as a regular comment and will fail to store your desired content in the `.Summary` variable.
@@ -72,5 +70,6 @@ You can show content summaries with the following code. You could use the follow
Note how the `.Truncated` boolean valuable may be used to hide the "Read More..." link when the content is not truncated; i.e., when the summary contains the entire article.
+[org]: /content-management/supported-content-formats/
[pagevariables]: /variables-and-params/page-variables/
[section's list page template]: /templates/list-and-section-templates/
\ No newline at end of file
diff --git a/content/content-management/content-types.md b/content/content-management/content-types.md
index b46538035..98970e70b 100644
--- a/content/content-management/content-types.md
+++ b/content/content-management/content-types.md
@@ -5,11 +5,10 @@ description:
date: 2017-02-01
publishdate: 2017-02-01
lastmod: 2017-02-01
-tags: [lists,sections,content types,types,organization]
categories: [content management]
-weight: 40
+tags: [lists,sections,content types,types,organization]
+weight: 60
draft: false
-slug:
aliases: [/content/types]
toc: true
needsreview: true
@@ -34,7 +33,7 @@ You can manually add files to your content directories, but Hugo has the ability
Creating a new content type is easy in Hugo. You simply provide the templates and archetype that the new type will use. You only need to define the templates, archetypes and/or views unique to that content type. Hugo will fall back to using the general templates and default archetype whenever a specific file is not present.
{{% note "Declaring Content Types" %}}
-Remember, all of the following are *optional*. If you do not specifically declare content types in your front matter or develop specific layouts for content types, Hugo is smart enough to infer the content type from the file path and content section (see [content sections](/content-management/content-sections/)).
+Remember, all of the following are *optional*. If you do not specifically declare content types in your front matter or develop specific layouts for content types, Hugo is smart enough to infer the content type from the file path and content section (see [content sections](/content-management/sections/)).
{{% /note %}}
### Create Type Layout Directory
@@ -61,7 +60,7 @@ More details about archetypes can be found in the [archetypes documentation][].
[archetypes]: /content-management/archetypes/
[archetypes documentation]: /content-management/archetypes/
-[sections]: /content-sections/
+[sections]: /content-management/sections/
[front matter]: /content-management/front-matter/
[list of contents on a single page]: /templates/list-and-section-templates/
[template]: /templates/
diff --git a/content/content-management/cross-references.md b/content/content-management/cross-references.md
index fb010d088..210b977fd 100644
--- a/content/content-management/cross-references.md
+++ b/content/content-management/cross-references.md
@@ -7,12 +7,11 @@ publishdate: 2017-02-01
lastmod: 2017-01-09
categories: [content management]
tags: ["cross references","references", "anchors", "urls"]
-weight: 80
+weight: 100
draft: false
aliases: []
-toc:
+toc: true
needsreview: true
-notesforauthors:
---
Hugo makes it easy to link documents together with `ref` and `relref`, both of which are [built-in Hugo shortcodes][]. These shortcodes are also used to safely provide links to headings inside of your content, whether across documents or within a document. The only difference between `ref` and `relref` is whether the resulting URL is absolute (`http://1.com/about/`) or relative (`/about/`).
diff --git a/content/content-management/front-matter.md b/content/content-management/front-matter.md
index 44bd02a7e..e2896f3e4 100644
--- a/content/content-management/front-matter.md
+++ b/content/content-management/front-matter.md
@@ -7,9 +7,8 @@ publishdate: 2017-01-09
lastmod: 2017-01-09
categories: [content management]
tags: ["front matter", "yaml", "toml", "json", "metadata", "archetypes"]
-weight: 20
+weight: 30
draft: false
-slug:
aliases: [/content/front-matter/]
needsreview: true
toc:
@@ -104,11 +103,11 @@ There are a few predefined variables that Hugo is aware of and utilizes. The use
If neither `slug` nor `url` is present, and [permalinks are not configured otherwise](/content-management/url-management/#permalinks), the filename will be used to create the URL for a page.
{{% /note %}}
-## Configure Blackfriday Rendering
+## Override Global Blackfriday Configuration
It's possible to set some options for Markdown rendering in the page's front matter as an override to the site-wide configuration.
-See [site configuration][] for more information.
+See [site configuration][] for more information on setting up global Blackfriday options.
## Parameters
diff --git a/content/content-management/menus.md b/content/content-management/menus.md
index 9cf54fa70..c1a6c0a31 100644
--- a/content/content-management/menus.md
+++ b/content/content-management/menus.md
@@ -5,10 +5,10 @@ description:
date: 2017-02-01
publishdate: 2017-02-01
lastmod: 2017-02-01
-weight:
categories: [templating]
tags: [lists,sections,menus]
draft: false
+weight: 120
aliases: [/extras/menus/]
toc: true
needsreview: true
diff --git a/content/content-management/multilingual-mode.md b/content/content-management/multilingual-mode.md
index b163ccf39..aec87f70b 100644
--- a/content/content-management/multilingual-mode.md
+++ b/content/content-management/multilingual-mode.md
@@ -7,10 +7,9 @@ publishdate: 2017-01-10
lastmod: 2017-01-10
categories: [content management]
tags: [multilingual,i18n]
-weight: 120
+weight: 150
draft: false
-slug:
-aliases: [/content/multilingual/]
+aliases: [/content/multilingual/,/content-management/multilingual/]
toc: true
needsreview: true
notesforauthors:
@@ -46,20 +45,20 @@ help = "Aide"
```
Anything not defined in a `[Languages]` block will fall back to the global
-value for that key (like `copyright` for the English (`en`) language in this example).
+value for that key (e.g., `copyright` for the English [`en`] language).
-With the config above, all content, sitemap, RSS feeds, paginations
+With the config above, all content, sitemap, RSS feeds, paginations,
and taxonomy pages will be rendered below `/` in English (your default content language), and below `/fr` in French.
-When working with params in frontmatter pages, omit the `params` in the key for the translation.
+When working with params in front matter pages, omit the `params` in the key for the translation.
If you want all of the languages to be put below their respective language code, enable `defaultContentLanguageInSubdir: true` in your configuration.
Only the obvious non-global options can be overridden per language. Examples of global options are `BaseURL`, `BuildDrafts`, etc.
-Taxonomies and Blackfriday configuration can also be set per language, example:
+Taxonomies and [Blackfriday configuration][hugoconfig] can also be set per language:
-```
+```toml
[Taxonomies]
tag = "tags"
@@ -81,12 +80,11 @@ title = "Français"
plaque = "plaques"
```
-
-### Translating your content
+## Translating Your Content
Translated articles are identified by the name of the content file.
-Example of translated articles:
+### Examples of Translated Articles
1. `/content/about.en.md`
2. `/content/about.fr.md`
@@ -103,11 +101,12 @@ If left unspecified, the value for `defaultContentLanguage` defaults to `en`.
By having the same _base file name_, the content pieces are linked together as translated pieces.
-### Link to translated content
+## Link to Translated Content
To create a list of links to translated content, use a template similar to this:
-```
+{{% input "layouts/partials/i18nlist.html" %}}
+```html
{{ if .IsTranslated }}