mirror of
https://github.com/gohugoio/hugo.git
synced 2024-11-14 20:37:55 -05:00
eb16165694
d1cf9adc4 Fix typo 26e10a690 Fix the name and arg mismatch between partial defn and call 2db0e53cd Merge commit '9c36cff15224f6cbd19058ad61311229b7a23c83' 9c36cff15 Squashed 'themes/gohugoioTheme/' changes from 68ddff44..b8202f53 4b021eff8 Update lang.Merge.md b37af2916 Add title to yaml a9a281233 Fixed incorrect usage of the code-toggle shortcode 4560a0169 Update Warning for Theme Links (#676) 0305e3c6b Document .File.ContentBaseName 6d30c5aa1 Update configuration.md 158df174a Document .Sites and .Sites.First 0c0f583b8 Add stale config e2531afd8 Document path template functions 4dd779057 Clarify that partialCached is per site/language 19e5bbe0c Update index.md 44b000857 Add missing dot a41300cf9 Release 0.52 2d1d92b88 Merge branch 'temp52' c5925250d releaser: Prepare repository for 0.53-DEV d000b04a2 releaser: Add release notes to /docs for release of 0.52 4bb983a0a releaser: Bump versions for release of 0.52 36736ca28 tpl: Add "param" shortcode 378677aa6 Add Elasticsearch/bonsai.io to services doc. 4c3fd4fa4 docs: Document inline shortcodes 6c64c374c Whitelist CSS modules from purge 817a872b9 Improve search icon position cf86ff1c7 Add minification and resource cache clear to build command fd77e8df3 Update asset dependencies and adopt Hugo Pipes cdbe97e8c Update render.md b0e279220 git command to update submodule to latest a1cb98c12 cache/filecache: Add a :project placeholder 07c1b2b46 cache/filecache: Use time.Duration for maxAge ffa9b165e Add AND as a title 6e7733b40 Add OR as a sub title to make it easier to find in search 72b6791a1 docs: Document the new file cache 714d3ca91 Fix minification issues cd1e961da Revert "Add Elasticsearch/bonsai.io to services doc." 15a0cda6e Add Elasticsearch/bonsai.io to services doc. f931d86de Release 0.51 e2ffe867a Merge branch 'temp51' 423e7f5c8 releaser: Prepare repository for 0.52-DEV c6f2d6ae1 releaser: Add release notes to /docs for release of 0.51 5bbb556dc releaser: Bump versions for release of 0.51 3b2b172b9 docs: Document shortcode error handling b8672f3d4 docs: Document symdiff 4bc6071e6 docs: Document complement d1baab752 docs: Re-generate CLI docs 9ea667e24 Revert "tpl: Update Jsonify to return pretty-print output" ce5a1403d docs: Regenerate the docs helper 99a1f4a94 Fix note for reserved partial name(starting with -> including). eba3cbc42 fix accidentally modification on paragraph. 3eebd98c3 Add note for reserved partial name. 40b881cc2 Document templates.Exists b5c3bcd3b Update multilingual.md 61c59c67e Fix misspelling (#648) f21d8c4a4 Correct minor typo (#5372) e967001b9 Release 0.50 685fd6b08 releaser: Prepare repository for 0.51-DEV f245a9faa releaser: Add release notes to /docs for release of 0.50 4354da30d releaser: Bump versions for release of 0.50 feaa05469 docs: Regenerate CLI docs 5c724200c Merge commit 'd6a4af7018e8618944a6471ceeb7aae1d4df6afa' 2ddab36c2 Merge commit '74309fe5699a595080fdb3a14711e0869babce99' 8cf296a7c docs: Regenerate CLI docs 9097683dd tpl: Update Jsonify to return pretty-print output git-subtree-dir: docs git-subtree-split: d1cf9adc412245c96d9d32592a903370d3972aef
184 lines
8.2 KiB
Markdown
184 lines
8.2 KiB
Markdown
---
|
|
title: Front Matter
|
|
linktitle:
|
|
description: Hugo allows you to add front matter in yaml, toml, or json to your content files.
|
|
date: 2017-01-09
|
|
publishdate: 2017-01-09
|
|
lastmod: 2017-02-24
|
|
categories: [content management]
|
|
keywords: ["front matter", "yaml", "toml", "json", "metadata", "archetypes"]
|
|
menu:
|
|
docs:
|
|
parent: "content-management"
|
|
weight: 30
|
|
weight: 30 #rem
|
|
draft: false
|
|
aliases: [/content/front-matter/]
|
|
toc: true
|
|
---
|
|
|
|
**Front matter** allows you to keep metadata attached to an instance of a [content type][]---i.e., embedded inside a content file---and is one of the many features that gives Hugo its strength.
|
|
|
|
{{< youtube Yh2xKRJGff4 >}}
|
|
|
|
## Front Matter Formats
|
|
|
|
Hugo supports three formats for front matter, each with their own identifying tokens.
|
|
|
|
TOML
|
|
: identified by opening and closing `+++`.
|
|
|
|
YAML
|
|
: identified by opening and closing `---`.
|
|
|
|
JSON
|
|
: a single JSON object surrounded by '`{`' and '`}`', followed by a new line.
|
|
|
|
### Example
|
|
|
|
{{< code-toggle >}}
|
|
title = "spf13-vim 3.0 release and new website"
|
|
description = "spf13-vim is a cross platform distribution of vim plugins and resources for Vim."
|
|
tags = [ ".vimrc", "plugins", "spf13-vim", "vim" ]
|
|
date = "2012-04-06"
|
|
categories = [
|
|
"Development",
|
|
"VIM"
|
|
]
|
|
slug = "spf13-vim-3-0-release-and-new-website"
|
|
{{< /code-toggle >}}
|
|
|
|
## Front Matter Variables
|
|
|
|
### Predefined
|
|
|
|
There are a few predefined variables that Hugo is aware of. See [Page Variables][pagevars] for how to call many of these predefined variables in your templates.
|
|
|
|
aliases
|
|
: an array of one or more aliases (e.g., old published paths of renamed content) that will be created in the output directory structure . See [Aliases][aliases] for details.
|
|
|
|
audio
|
|
: an array of paths to audio files related to the page; used by the `opengraph` [internal template](/templates/internal) to populate `og:audio`.
|
|
|
|
date
|
|
: the datetime at which the content was created; note this value is auto-populated according to Hugo's built-in [archetype][].
|
|
|
|
description
|
|
: the description for the content.
|
|
|
|
draft
|
|
: if `true`, the content will not be rendered unless the `--buildDrafts` flag is passed to the `hugo` command.
|
|
|
|
expiryDate
|
|
: the datetime at which the content should no longer be published by Hugo; expired content will not be rendered unless the `--buildExpired` flag is passed to the `hugo` command.
|
|
|
|
headless
|
|
: if `true`, sets a leaf bundle to be [headless][headless-bundle].
|
|
|
|
images
|
|
: an array of paths to images related to the page; used by [internal templates](/templates/internal) such as `_internal/twitter_cards.html`.
|
|
|
|
isCJKLanguage
|
|
: if `true`, Hugo will explicitly treat the content as a CJK language; both `.Summary` and `.WordCount` work properly in CJK languages.
|
|
|
|
keywords
|
|
: the meta keywords for the content.
|
|
|
|
layout
|
|
: 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. See ["Defining a Content Type"][definetype]
|
|
|
|
lastmod
|
|
: the datetime at which the content was last modified.
|
|
|
|
linkTitle
|
|
: used for creating links to content; if set, Hugo defaults to using the `linktitle` before the `title`. Hugo can also [order lists of content by `linktitle`][bylinktitle].
|
|
|
|
markup
|
|
: **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
|
|
: if in the future, content will not be rendered unless the `--buildFuture` flag is passed to `hugo`.
|
|
|
|
resources
|
|
: used for configuring page bundle resources. See [Page Resources][page-resources].
|
|
|
|
series
|
|
: an array of series this page belongs to, as a subset of the `series` [taxonomy](/content-management/taxonomies/); used by the `opengraph` [internal template](/templates/internal) to populate `og:see_also`.
|
|
|
|
slug
|
|
: appears as the tail of the output URL. A value specified in front matter will override the segment of the URL based on the filename.
|
|
|
|
title
|
|
: the title for the content.
|
|
|
|
type
|
|
: the type of the content; this value will be automatically derived from the directory (i.e., the [section][]) if not specified in front matter.
|
|
|
|
url
|
|
: the full path to the content from the web root. It makes no assumptions about the path of the content file. It also ignores any language prefixes of
|
|
the multilingual feature.
|
|
|
|
videos
|
|
: an array of paths to videos related to the page; used by the `opengraph` [internal template](/templates/internal) to populate `og:video`.
|
|
|
|
weight
|
|
: used for [ordering your content in lists][ordering]. Lower weight gets higher precedence. So content with lower weight will come first.
|
|
|
|
\<taxonomies\>
|
|
: field name of the *plural* form of the index. See `tags` and `categories` in the above front matter examples. _Note that the plural form of user-defined taxonomies cannot be the same as any of the predefined front matter variables._
|
|
|
|
{{% note "Hugo's Default URL Destinations" %}}
|
|
If neither `slug` nor `url` is present and [permalinks are not configured otherwise in your site `config` file](/content-management/urls/#permalinks), Hugo will use the filename of your content to create the output URL. See [Content Organization](/content-management/organization) for an explanation of paths in Hugo and [URL Management](/content-management/urls/) for ways to customize Hugo's default behaviors.
|
|
{{% /note %}}
|
|
|
|
### User-Defined
|
|
|
|
You can add fields to your front matter arbitrarily to meet your needs. These user-defined key-values are placed into a single `.Params` variable for use in your templates.
|
|
|
|
The following fields can be accessed via `.Params.include_toc` and `.Params.show_comments`, respectively. The [Variables][] section provides more information on using Hugo's page- and site-level variables in your templates.
|
|
|
|
{{< code-toggle copy="false" >}}
|
|
include_toc: true
|
|
show_comments: false
|
|
{{</ code-toggle >}}
|
|
|
|
|
|
## Order Content Through Front Matter
|
|
|
|
You can assign content-specific `weight` in the front matter of your content. These values are especially useful for [ordering][ordering] in list views. You can use `weight` for ordering of content and the convention of [`<TAXONOMY>_weight`][taxweight] for ordering content within a taxonomy. See [Ordering and Grouping Hugo Lists][lists] to see how `weight` can be used to organize your content in list views.
|
|
|
|
## Override Global Markdown Configuration
|
|
|
|
It's possible to set some options for Markdown rendering in a content's front matter as an override to the [BlackFriday rendering options set in your project configuration][config].
|
|
|
|
## Front Matter Format Specs
|
|
|
|
* [TOML Spec][toml]
|
|
* [YAML Spec][yaml]
|
|
* [JSON Spec][json]
|
|
|
|
[variables]: /variables/
|
|
[aliases]: /content-management/urls/#aliases/
|
|
[archetype]: /content-management/archetypes/
|
|
[bylinktitle]: /templates/lists/#by-link-title
|
|
[config]: /getting-started/configuration/ "Hugo documentation for site configuration"
|
|
[content type]: /content-management/types/
|
|
[contentorg]: /content-management/organization/
|
|
[definetype]: /content-management/types/#defining-a-content-type "Learn how to specify a type and a layout in a content's front matter"
|
|
[headless-bundle]: /content-management/page-bundles/#headless-bundle
|
|
[json]: https://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf "Specification for JSON, JavaScript Object Notation"
|
|
[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/ "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"
|
|
[outputs]: /templates/output-formats/ "With the release of v22, you can output your content to any text format using Hugo's familiar templating"
|
|
[page-resources]: /content-management/page-resources/
|
|
[pagevars]: /variables/page/
|
|
[section]: /content-management/sections/
|
|
[taxweight]: /content-management/taxonomies/
|
|
[toml]: https://github.com/toml-lang/toml "Specification for TOML, Tom's Obvious Minimal Language"
|
|
[urls]: /content-management/urls/
|
|
[variables]: /variables/
|
|
[yaml]: http://yaml.org/spec/ "Specification for YAML, YAML Ain't Markup Language"
|