Add information about layout front matter variable

Also add outputs to front matter documentation.

Closes rdwatters/hugo-docs-concept#130
Closes gohugoio/hugo#3558
This commit is contained in:
Ryan Watters 2017-06-10 16:25:57 -05:00
parent 44e6279dfb
commit e47b74d8d0
3 changed files with 9 additions and 5 deletions

View File

@ -108,7 +108,7 @@ There are a few predefined variables that Hugo is aware of. See [Page Variables]
: the meta keywords for the content. : the meta keywords for the content.
`layout` `layout`
: the layout Hugo should select from the [lookup order][lookup] when rendering the content. : the layout Hugo should select from the [lookup order][lookup] when rendering the content. If a `type` is not specified in the front matter, Hugo will look for the layout of the same name in the layout directory that corresponds with a content's section.
`lastmod` `lastmod`
: the datetime at which the content was last modified. : the datetime at which the content was last modified.
@ -119,6 +119,9 @@ There are a few predefined variables that Hugo is aware of. See [Page Variables]
`markup` `markup`
: **experimental**; specify `"rst"` for reStructuredText (requires`rst2html`) or `"md"` (default) for Markdown. : **experimental**; specify `"rst"` for reStructuredText (requires`rst2html`) or `"md"` (default) for Markdown.
`outputs`
: allows you to specify output formats specific to the content. See [output formats][outputs]
`publishdate` `publishdate`
: if in the future, content will not be rendered unless the `--buildFuture` flag is passed to `hugo`. : if in the future, content will not be rendered unless the `--buildFuture` flag is passed to `hugo`.
@ -184,9 +187,10 @@ It's possible to set some options for Markdown rendering in a content's front ma
[content type]: /content-management/types/ [content type]: /content-management/types/
[contentorg]: /content-management/organization/ [contentorg]: /content-management/organization/
[json]: /documents/ecma-404-json-spec.pdf "Specification for JSON, JavaScript Object Notation" [json]: /documents/ecma-404-json-spec.pdf "Specification for JSON, JavaScript Object Notation"
[lists]: /templates/lists/#ordering-content [lists]: /templates/lists/#ordering-content "See how to order content in list pages; for example, templates that look to specific _index.md for content and front matter."
[lookup]: /templates/lookup-order/ [lookup]: /templates/lookup-order/ "Hugo traverses your templates in a specific order when rendering content to allow for DRYer templating."
[ordering]: /templates/lists/ "Hugo provides multiple ways to sort and order your content in list templates" [ordering]: /templates/lists/ "Hugo provides multiple ways to sort and order your content in list templates"
[outputs]: /templates/output-formats/ "With the release of v22, you can output your content to any text format using Hugo's familiar templating"
[pagevars]: /variables/page/ [pagevars]: /variables/page/
[section]: /content-management/sections/ [section]: /content-management/sections/
[taxweight]: /content-management/taxonomies/ [taxweight]: /content-management/taxonomies/

View File

@ -1,6 +1,6 @@
--- ---
title: Custom Output Formats title: Custom Output Formats
linktitle: Output Formats linktitle: Custom Output Formats
description: Hugo can output content in multiple formats, including calendar events, e-book formats, Google AMP, and JSON search indexes, while allowing extensibility for any format your site needs. description: Hugo can output content in multiple formats, including calendar events, e-book formats, Google AMP, and JSON search indexes, while allowing extensibility for any format your site needs.
date: 2017-03-22 date: 2017-03-22
publishdate: 2017-03-22 publishdate: 2017-03-22