tiennm99/hugoDocs
1
0 Fork 0
mirror of https://github.com/tiennm99/hugoDocs.git synced 2026-10-13 20:14:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

Correct delimiters for YAML front matter example

Browse Source 
Closes rdwatters/hugo-docs-concept#5
This commit is contained in:
Ryan Watters committed 2017-03-06 12:04:58 -06:00
1 parent 1a147b9b44
commit 67c60f4806
2 files changed
+4 -4
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

content/content-management/taxonomies.md
+2 -2
View File
@@ -180,14 +180,14 @@ project_url = "https://github.com/spf13/hugo"
### YAML Front Matter with Taxonomies Example ### YAML Front Matter with Taxonomies Example
```yaml ```yaml
+++ ---
title: "Hugo: A fast and flexible static site generator" title: "Hugo: A fast and flexible static site generator"
tags: ["Development", "Go", "fast", "Blogging"] tags: ["Development", "Go", "fast", "Blogging"]
categories: ["Development"] categories: ["Development"]
categories: ["Go Web Dev"] categories: ["Go Web Dev"]
slug: "hugo" slug: "hugo"
project_url: "https://github.com/spf13/hugo" project_url: "https://github.com/spf13/hugo"
+++ ---
``` ```
### JSON Front Matter with Taxonomies Example ### JSON Front Matter with Taxonomies Example
content/content-management/urls.md
+2 -2
View File
@@ -234,7 +234,7 @@ hugo config | FINDSTR /I canon
## Overriding URLS with Front Matter ## Overriding URLS with Front Matter
In addition to specifying permalink values in your site configuration for different sections of content, Hugo provides even more granular for individual pieces of content. In addition to specifying permalink values in your site configuration for different content sections, Hugo provides even more granular control for individual pieces of content.
Both `slug` and `url` can be defined in individual front matter. For more information on content destinations at build time, seee [Content Organization][contentorg]. Both `slug` and `url` can be defined in individual front matter. For more information on content destinations at build time, seee [Content Organization][contentorg].
@@ -244,7 +244,7 @@ By default, all relative URLs are left unchanged by Hugo, which can be problemat
Setting `relativeURLs` to `true` in your [site configuration][config] will cause Hugo to rewrite all relative URLs to be relative to the current content. Setting `relativeURLs` to `true` in your [site configuration][config] will cause Hugo to rewrite all relative URLs to be relative to the current content.
For example, if the `/post/first/` page contained a link to `/about/`, Hugo would rewrite that URL to `../../about/`. For example, if your `/post/first/` page contains a link to `/about/`, Hugo will rewrite the URL to `../../about/`.
[config]: /getting-started/configuration/ [config]: /getting-started/configuration/
[contentorg]: /content-management/organization/ [contentorg]: /content-management/organization/