49809a03 Merge commit '20a631b4964fc0ab9137cce1e41774cbc17de044' 20a631b4 Squashed 'themes/gohugoioTheme/' changes from b8202f539..dafc91ff1 8b58f565 Re-generate CLI docs 4653a724 Add Netlify deployment badge 2d6246bc Remove some deprecated site variables e6777153 Improve Algolia Search Display Styling 1570999f Add missing "." in front of gitlab-ci.yaml example b922ae7d This adds documentation to the new configDir/Environment logic from .53 (#729) 7cff379f Correctly escape multi-word taxonomy terms in example 2dfeeda4 fix typo by removing stray paren 0870bd9a Fix typo in `paginate` description 91e8be85 Fixes https://github.com/gohugoio/hugo/issues/5609 c1db65ec Make the dummy URL more obvious b4589ff0 Fix a link b73dcb9a Consistently use "posts" as section name in examples 7a56abbc Format definitions a9c6fd9b Minor clarification over the last commit 5c86bdc8 Add alternative instructions for Quick Start for non-git users dafe7ee9 Add Visual Studio Code plug-ins 110ed19e Update HUGO_VERSION 2abd031a Update page.md b332f7b9 Update page.md f5a8c9d4 Update static-files.md 6d0c155c Add note about relative protocol URLs a13751ac Theme Warning: Remove note about unquoted URLs 4c8f7d68 Incorporate feedback 6f2b9cf0 Update Creating Themes Warning 40d88d98 Fix ToC example to use binary true/false 4a11f3f1 Fix typo 2dbfc0a4 Fix a typo in taxonomies d63790ef Do not mark UndocumentedFeature issues as stale d7aff095 Regenerate docs.json 71c0826f Update transform.Unmarshal.md git-subtree-dir: docs git-subtree-split: 49809a038b2691637bab7f3f2e385dde654a88b8
11 KiB
title | linktitle | description | date | publishdate | lastmod | categories | keywords | draft | menu | weight | sections_weight | aliases | 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. | 2017-02-01 | 2017-02-01 | 2017-02-01 |
|
|
false |
|
20 | 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.
{{% note ".Scratch
" %}}
See .Scratch
for page-scoped, writable variables.
{{% /note %}}
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.) - .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.
- .Dir
- the path of the folder containing this content file. The path is relative to the
content
folder. - .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.
- .FuzzyWordCount
- the approximate number of words in the content.
- .Hugo
- see Hugo Variables.
- .IsHome
true
in the context of the homepage.- .IsNode
- always
false
for regular content pages. - .IsPage
- always
true
for regular content pages. - .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
, ortaxonomyTerm
. 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
config
. - .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 (deprecated)
- In older Hugo versions this pointer went the wrong direction. Please use
.PrevPage
instead. - .NextPage
- Pointer to the next regular page (sorted by Hugo's default sort). Example:
{{if .NextPage}}{{.NextPage.Permalink}}{{end}}
. - .NextInSection
- Pointer to the next regular page within the same section. Pages are sorted by Hugo's default sort. Example:
{{if .NextInSection}}{{.NextInSection.Permalink}}{{end}}
. - .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.
- .PlainWords
- the Page content stripped of HTML as a
[]string
using Go'sstrings.Fields
to split.Plain
into a slice. - .Prev (deprecated)
- In older Hugo versions this pointer went the wrong direction. Please use
.NextPage
instead. - .PrevPage
- Pointer to the previous regular page (sorted by Hugo's default sort). Example:
{{if .PrevPage}}{{.PrevPage.Permalink}}{{end}}
. - .PrevInSection
- Pointer to the previous regular page within the same section. Pages are sorted by Hugo's default sort. Example:
{{if .PrevInSection}}{{.PrevInSection.Permalink}}{{end}}
. - .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
. - .RSSLink
- link to the taxonomies' RSS link.
- .RawContent
- raw markdown content without the front matter. Useful with remarkjs.com
- .ReadingTime
- the estimated time, in minutes, it takes to read the content.
- .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. 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.
- .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
). - .UniqueID
- the MD5-checksum of the content file's path.
- .Weight
- assigned weight (in the front matter) to this content, used in sorting.
- .WordCount
- the number of words in the content.
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
{{< readfile file="/content/en/readfiles/pages-vs-site-pages.md" markdown="true" >}}
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.
---
title: My First Post
date: 2017-02-20T15:26:23-06:00
categories: [one]
tags: [two,three,four]
With the above front matter, the tags
and categories
taxonomies are accessible via the following:
.Params.tags
.Params.categories
{{% note "Casing of Params" %}}
Page-level .Params
are only accessible in lowercase.
{{% /note %}}
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 in /content/review/book01.md
:
---
...
affiliatelink: "http://www.my-book-link.here"
recommendedby: "My Mother"
...
---
These fields would then be accessible to the /themes/yourtheme/layouts/review/single.html
template through .Params.affiliatelink
and .Params.recommendedby
, respectively.
Two common situations where this type of front matter field could be introduced is as a value of a certain attribute like href=""
or by itself to be displayed as text to the website's visitors.
{{< code file="/themes/yourtheme/layouts/review/single.html" >}}
Buy this book
It was recommended by {{ .Params.recommendedby }}.
{{< /code >}}This template would render as follows, assuming you've set uglyURLs
to false
in your site config
:
{{< output file="yourbaseurl/review/book01/index.html" >}}
Buy this book
It was recommended by my Mother.
{{< /output >}}{{% 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 config
).
Access Nested Fields in Front Matter
When front matter contains nested fields like the following:
---
author:
given_name: John
family_name: Feminella
display_name: John Feminella
---
.Param
can access these fields by concatenating the field names together with a dot:
{{ $.Param "author.display_name" }}
If your front matter contains a top-level key that is ambiguous with a nested key, as in the following case:
---
favorites.flavor: vanilla
favorites:
flavor: chocolate
---
The top-level key will be preferred. Therefore, the following method, when applied to the previous example, will print vanilla
and not chocolate
:
{{ $.Param "favorites.flavor" }}
=> vanilla