Hugo FrontMatter Variables
| |
There are a few predefined variables that Hugo is aware of. See Page Variables for how to call many of these predefined variables in your templates.
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 for details.
an array of paths to audio files related to the page; used by the opengraph internal template to populate og:audio.
a map of Front Matter keys whose values are passed down to the page’s descendants unless overwritten by self or a closer ancestor’s cascade. See Front Matter Cascade for details.
the datetime assigned to this page. This is usually fetched from the date field in front matter, but this behaviour is configurable.
the description for the content.
if true, the content will not be rendered unless the –buildDrafts flag is passed to the hugo command.
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.
if true, sets a leaf bundle to be headless.
an array of paths to images related to the page; used by internal templates such as _internal/twitter_cards.html.
if true, Hugo will explicitly treat the content as a CJK language; both .Summary and .WordCount work properly in CJK languages.
the meta keywords for the content.
the layout Hugo should select from the lookup order 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 Content Types.
the datetime at which the content was last modified.
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.
experimental; specify “rst” for reStructuredText (requiresrst2html) or “md” (default) for Markdown.
allows you to specify output formats specific to the content. See output formats.
if in the future, content will not be rendered unless the –buildFuture flag is passed to hugo.
used for configuring page bundle resources. See Page Resources.
an array of series this page belongs to, as a subset of the series taxonomy; used by the opengraph internal template to populate og:see_also.
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.
text used when providing a summary of the article in the .Summary page variable; details available in the content-summaries section.
the title for the content.
the type of the content; this value will be automatically derived from the directory (i.e., the section) if not specified in front matter.
the full path to the content from the web root. It makes no assumptions about the path of the content file. See URL Management.
an array of paths to videos related to the page; used by the opengraph internal template to populate og:video.
used for ordering your content in lists. Lower weight gets higher precedence. So content with lower weight will come first. If set, weights should be non-zero, as 0 is interpreted as an unset weight.
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. If neither slug nor url is present and permalinks are not configured otherwise in your site config file, Hugo will use the filename of your content to create the output URL. See Content Organization for an explanation of paths in Hugo and URL Management for ways to customize Hugo’s default behaviors.
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.
Any node or section can pass down to descendants a set of Front Matter values as long as defined underneath the reserved cascade Front Matter key.
New in v0.76.0 Since Hugo 0.76 the cascade block can be a slice with a optional _target keyword, allowing for multiple cascade values targeting different page sets.
path A Glob pattern matching the content path below /content. Expects Unix-styled slashes. Note that this is the virtual path, so it starts at the mount root. The matching support double-asterisks so you can match for patterns like /blog/*/** to match anything from the third level and down. kind A Glob pattern matching the Page’s Kind(s), e.g. “{home,section}”. lang A Glob pattern matching the Page’s language, e.g. “{en,sv}”. environment A Glob pattern matching the build environment, e.g. “{production,development}” Any of the above can be omitted.
Example In content/blog/_index.md
yaml toml json
cascade: banner: images/typewriter.jpg title: Blog With the above example the Blog section page and its descendants will return images/typewriter.jpg when .Params.banner is invoked unless:
Said descendant has its own banner value set
Or a closer ancestor node has its own cascade.banner value set.
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 in list views. You can use weight for ordering of content and the convention of
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.