1798dc0d5 Update theme 403fa716e Update CLI documentation (#2092) aade5a09e Correct media subtype example 53cd9dea6 netlify: Hugo 0.112.3 b78b86cb1 Add source/target warning to resources.Copy (#2091) 50c299729 netlify: Hugo 0.112.2 73197046f Change config.xxx to hugo.xxx throughout the documentation (#2090) d489d4c6f Add hugo.WorkingDir to docs (#2089) 7487df809 Fix typos (#2088) 6d0572cd6 netlify: Hugo 0.112.1 6838600b2 netlify: Hugo 0.112.0 513e7a80f Merge branch 'tempv0.112.0' 91eb44275 Some more about 0.112.0 bd3b33a27 docs: Regen docshelper fb3027daf docs: Regen CLI docs 8e7b8e987 Merge commit 'f96384a3b596f9bc0a3a035970b09b2c601f0ccb' a942ceef4 tpl/tplimpl: Add img loading attribute to figure shortcode (#10927) 0e0c7b25e tpl/urls: Return empty string when JoinPath has zero args 310ce949a tpl/urls: Add JoinPath template function ae435ca77 tpl: Add math.Abs f340139f8 Revert "Update syntax-highlighting.md (#10929)" (#10930) 917a0e24d Update syntax-highlighting.md (#10929) git-subtree-dir: docs git-subtree-split: 1798dc0d54ce048dd975863b490cd809ef14268a
13 KiB
title | description | categories | keywords | menu | weight | toc | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Page Variables | Page-level variables are defined in a content file's front matter, derived from the content's file location, or extracted from the content body itself. |
|
|
|
20 | true |
The following is a list of page-level variables. Many of these will be defined in the front matter, derived from file location, or extracted from the content itself.
Page Variables
- .AlternativeOutputFormats
- contains all alternative formats for a given page; this variable is especially useful
link rel
list in your site's<head>
. (See Output Formats.) - .Aliases
- aliases of this page
- .Ancestors
- get the ancestors of each page, simplify breadcrumb navigation implementation complexity
- .BundleType
- the bundle type:
leaf
,branch
, or an empty string if the page is not a bundle. - .Content
- the content itself, defined below the front matter.
- .Data
- the data specific to this type of page.
- .Date
- the date associated with the page;
.Date
pulls from thedate
field in a content's front matter. See also.ExpiryDate
,.PublishDate
, and.Lastmod
. - .Description
- the description for the page.
- .Draft
- a boolean,
true
if the content is marked as a draft in the front matter. - .ExpiryDate
- the date on which the content is scheduled to expire;
.ExpiryDate
pulls from theexpirydate
field in a content's front matter. See also.PublishDate
,.Date
, and.Lastmod
. - .File
- filesystem-related data for this content file. See also File Variables.
- .Fragments
- Fragments returns the fragments for this page. See Page Fragments.
- .FuzzyWordCount
- the approximate number of words in the content.
- .IsHome
true
in the context of the homepage.- .IsNode
- always
false
for regular content pages. - .IsPage
- always
true
for regular content pages. - .IsSection
true
if.Kind
issection
.- .IsTranslated
true
if there are translations to display.- .Keywords
- the meta keywords for the content.
- .Kind
- the page's kind. Possible return values are
page
,home
,section
,taxonomy
, orterm
. Note that there are alsoRSS
,sitemap
,robotsTXT
, and404
kinds, but these are only available during the rendering of each of these respective page's kind and therefore not available in any of thePages
collections. - .Language
- a language object that points to the language's definition in the site configuration.
.Language.Lang
gives you the language code. - .Lastmod
- the date the content was last modified.
.Lastmod
pulls from thelastmod
field in a content's front matter.
- If
lastmod
is not set, and.GitInfo
feature is disabled, the front matterdate
field will be used. - If
lastmod
is not set, and.GitInfo
feature is enabled,.GitInfo.AuthorDate
will be used instead.
See also .ExpiryDate
, .Date
, .PublishDate
, and .GitInfo
.
- .LinkTitle
- access when creating links to the content. If set, Hugo will use the
linktitle
from the front matter beforetitle
. - .Next
- Points up to the next regular page (sorted by Hugo's default sort). Example:
{{ with .Next }}{{ .Permalink }}{{ end }}
. Calling.Next
from the first page returnsnil
. - .NextInSection
- Points up to the next regular page below the same top level section (e.g. in
/blog
)). Pages are sorted by Hugo's default sort. Example:{{ with .NextInSection }}{{ .Permalink }}{{ end }}
. Calling.NextInSection
from the first page returnsnil
. - .OutputFormats
- contains all formats, including the current format, for a given page. Can be combined the with
.Get
function to grab a specific format. (See Output Formats.) - .Pages
- a collection of associated pages. This value will be
nil
within the context of regular content pages. See.Pages
. - .Permalink
- the Permanent link for this page; see Permalinks
- .Plain
- the Page content stripped of HTML tags and presented as a string. You may need to pipe the result through the
htmlUnescape
function when rendering this value with the HTML output format. - .PlainWords
- the slice of strings that results from splitting .Plain into words, as defined in Go's strings.Fields.
- .Prev
- Points down to the previous regular page (sorted by Hugo's default sort). Example:
{{ if .Prev }}{{ .Prev.Permalink }}{{ end }}
. Calling.Prev
from the last page returnsnil
. - .PrevInSection
- Points down to the previous regular page below the same top level section (e.g.
/blog
). Pages are sorted by Hugo's default sort. Example:{{ if .PrevInSection }}{{ .PrevInSection.Permalink }}{{ end }}
. Calling.PrevInSection
from the last page returnsnil
. - .PublishDate
- the date on which the content was or will be published;
.Publishdate
pulls from thepublishdate
field in a content's front matter. See also.ExpiryDate
,.Date
, and.Lastmod
. - .RawContent
- raw markdown content without the front matter. Useful with remarkjs.com
- .ReadingTime
- the estimated time, in minutes, it takes to read the content.
- .Resources
- resources such as images and CSS that are associated with this page
- .Ref
- returns the permalink for a given reference (e.g.,
.Ref "sample.md"
)..Ref
does not handle in-page fragments correctly. See Cross References. - .RelPermalink
- the relative permanent link for this page.
- .RelRef
- returns the relative permalink for a given reference (e.g.,
RelRef "sample.md"
)..RelRef
does not handle in-page fragments correctly. See Cross References. - .Site
- see Site Variables.
- .Sites
- returns all sites (languages). A typical use case would be to link back to the main language:
<a href="{{ .Sites.First.Home.RelPermalink }}">...</a>
. - .Sites.First
- returns the site for the first language. If this is not a multilingual setup, it will return itself.
- .Summary
- a generated summary of the content for easily showing a snippet in a summary view. The breakpoint can be set manually by inserting
<!--more-->
at the appropriate place in the content page, or the summary can be written independent of the page text. See Content Summaries for more details. - .TableOfContents
- the rendered table of contents for the page.
- .Title
- the title for this page.
- .Translations
- a list of translated versions of the current page. See Multilingual Mode for more information.
- .TranslationKey
- the key used to map language translations of the current page. See Multilingual Mode for more information.
- .Truncated
- a boolean,
true
if the.Summary
is truncated. Useful for showing a "Read more..." link only when necessary. See Summaries for more information. - .Type
- the content type of the content (e.g.,
posts
). - .Weight
- assigned weight (in the front matter) to this content, used in sorting.
- .WordCount
- the number of words in the content.
Writable Page-scoped Variables
- .Scratch
- returns a Scratch to store and manipulate data. In contrast to the
.Store
method, this scratch is reset on server rebuilds. - .Store
- returns a Scratch to store and manipulate data. In contrast to the
.Scratch
method, this scratch is not reset on server rebuilds.
Section Variables and Methods
Also see Sections.
{{< readfile file="/content/en/readfiles/sectionvars.md" markdown="true" >}}
The .Pages
Variable
.Pages
is an alias to .Data.Pages
. It is conventional to use the
aliased form .Pages
.
.Pages
compared to .Site.Pages
{{< getcontent path="readfiles/pages-vs-site-pages.md" >}}
Page Fragments
{{< new-in "0.111.0" >}}
The .Fragments
method returns a list of fragments for the current page.
- .Headings
- A recursive list of headings for the current page. Can be used to generate a table of contents.
{{< todo >}}add .Headings toc example{{< /todo >}}
- .Identifiers
- A sorted list of identifiers for the current page. Can be used to check if a page contains a specific identifier or if a page contains duplicate identifiers:
{{ if .Fragments.Identifiers.Contains "my-identifier" }}
<p>Page contains identifier "my-identifier"</p>
{{ end }}
{{ if gt (.Fragments.Identifiers.Count "my-identifier") 1 }}
<p>Page contains duplicate "my-identifier" fragments</p>
{{ end }}
- .HeadingsMap
- Holds a map of headings for the current page. Can be used to start the table of contents from a specific heading.
Also see the Go Doc for the return type.
Fragments in hooks and shortcodes
.Fragments
are safe to call from render hooks, even on the page you're on (.Page.Fragments
). For shortcodes we recommend that all .Fragments
usage is nested inside the {{</**/>}}
shortcode delimiter ({{%/**/%}}
takes part in the ToC creation so it's easy to end up in a situation where you bite yourself in the tail).
The global page function
{{< new-in "0.111.1" >}}
Hugo almost always passes a Page
as the data context into the top level template (e.g. single.html
) (the one exception is the multihost sitemap template). This means that you can access the current page with the .
variable in the template.
But when you're deeply nested inside .Render
, partial etc., accessing that Page
object isn't always practical or possible.
For this reason, Hugo provides a global page
function that you can use to access the current page from anywhere in any template.
{{ page.Title }}
There are one caveat with this, and this isn't new, but it's worth mentioning here: There are situations in Hugo where you may see a cached value, e.g. when using partialCached
or in a shortcode.
Page-level Params
Any other value defined in the front matter in a content file, including taxonomies, will be made available as part of the .Params
variable.
{{< code-toggle file="content/example.md" fm=true copy=false >}} title: Example categories: [one] tags: [two,three,four] {{< /code-toggle >}}
With the above front matter, the tags
and categories
taxonomies are accessible via the following:
.Params.tags
.Params.categories
The .Params
variable is particularly useful for the introduction of user-defined front matter fields in content files. For example, a Hugo website on book reviews could have the following front matter:
{{< code-toggle file="content/example.md" fm=true copy=false >}} title: Example affiliatelink: "http://www.my-book-link.here" recommendedby: "My Mother" {{< /code-toggle >}}
These fields would then be accessible to via .Params.affiliatelink
and .Params.recommendedby
.
<h3><a href="{{ .Params.affiliatelink }}">Buy this book</a></h3>
<p>It was recommended by {{ .Params.recommendedby }}.</p>
This template would render as follows:
<h3><a href="http://www.my-book-link.here">Buy this book</a></h3>
<p>It was recommended by my Mother.</p>
{{% note %}}
See Archetypes for consistency of Params
across pieces of content.
{{% /note %}}
The .Param
Method
In Hugo, you can declare params in individual pages and globally for your entire website. A common use case is to have a general value for the site param and a more specific value for some of the pages (i.e., a header image):
{{ $.Param "header_image" }}
The .Param
method provides a way to resolve a single value according to it's definition in a page parameter (i.e. in the content's front matter) or a site parameter (i.e., in your site configuration).
Access Nested Fields in Front Matter
When front matter contains nested fields like the following:
{{< code-toggle file="content/example.md" fm=true copy=false >}} title: Example author: given_name: John family_name: Feminella display_name: John Feminella {{< /code-toggle >}}
.Param
can access these fields by concatenating the field names together with a dot:
{{ $.Param "author.display_name" }}