https://v0-122-0--gohugoio.netlify.app/methods/page/Recent content in Page methods on HugoHugo -- gohugo.ioenhttps://v0-122-0--gohugoio.netlify.app/methods/page/aliases/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/aliases/The Aliases method on a Page object returns the URL aliases as defined in front matter. For example: content/about.md yaml   toml   json   --- aliases: - /old-url - /really-old-url title: About --- +++ aliases = ['/old-url', '/really-old-url'] title = 'About' +++ { "aliases": [ "/old-url", "/really-old-url" ], "title": "About" } To list the aliases: {{ range .Aliases }} {{ . }} {{ end }}https://v0-122-0--gohugoio.netlify.app/methods/page/alltranslations/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/alltranslations/With this site configuration: hugo. yaml   toml   json   defaultContentLanguage: en languages: de: contentDir: content/de languageCode: de-DE languageName: Deutsch weight: 2 en: contentDir: content/en languageCode: en-US languageName: English weight: 1 fr: contentDir: content/fr languageCode: fr-FR languageName: Français weight: 3 defaultContentLanguage = 'en' [languages] [languages.de] contentDir = 'content/de' languageCode = 'de-DE' languageName = 'Deutsch' weight = 2 [languages.en] contentDir = 'content/en' languageCode = 'en-US' languageName = 'English' weight = 1 [languages.https://v0-122-0--gohugoio.netlify.app/methods/page/alternativeoutputformats/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/alternativeoutputformats/Hugo generates one or more files per page when building a site. For example, when rendering home, section, taxonomy, and term pages, Hugo generates an HTML file and an RSS file. Both HTML and RSS are built-in output formats. Create multiple output formats, and control generation based on page kind, or by enabling one or more output formats for one or more pages. See details. The AlternativeOutputFormats method on a Page object returns a slice of OutputFormat objects, excluding the current output format, each representing one of the output formats enabled for the given page.https://v0-122-0--gohugoio.netlify.app/methods/page/ancestors/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/ancestors/New in v0.109.0 A section is a top-level content directory, or any content directory with an _index.md file. With this content structure: content/ ├── auctions/ │ ├── 2023-11/ │ │ ├── _index.md <-- front matter: weight = 202311 │ │ ├── auction-1.md │ │ └── auction-2.md │ ├── 2023-12/ │ │ ├── _index.md <-- front matter: weight = 202312 │ │ ├── auction-3.md │ │ └── auction-4.md │ ├── _index.https://v0-122-0--gohugoio.netlify.app/methods/page/bundletype/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/bundletype/A page bundle is a directory that encapsulates both content and associated resources. There are two types of page bundles: leaf bundles and branch bundles. See details. The BundleType method on a Page object returns branch for branch bundles, leaf for leaf bundles, and an empty string if the page is not a page bundle. content/ ├── films/ │ ├── film-1/ │ │ ├── a.jpg │ │ └── index.md <-- leaf bundle │ ├── _index.https://v0-122-0--gohugoio.netlify.app/methods/page/codeowners/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/codeowners/GitHub and GitLab support CODEOWNERS files. This file specifies the users responsible for developing and maintaining software and documentation. This definition can apply to the entire repository, specific directories, or to individual files. To learn more: GitHub CODEOWNERS documentation GitLab CODEOWNERS documentation Use the CodeOwners method on a Page object to determine the code owners for the given page. To use the CodeOwners method you must enable access to your local Git repository:https://v0-122-0--gohugoio.netlify.app/methods/page/content/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/content/The Content method on a Page object renders markdown and shortcodes to HTML. The content does not include front matter. {{ .Content }}https://v0-122-0--gohugoio.netlify.app/methods/page/currentsection/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/currentsection/A section is a top-level content directory, or any content directory with an _index.md file. The current section of a section page, taxonomy page, term page, or the home page, is itself. Consider this content structure: content/ ├── auctions/ │ ├── 2023-11/ │ │ ├── _index.md <-- current section: 2023-11 │ │ ├── auction-1.md │ │ └── auction-2.md <-- current section: 2023-11 │ ├── 2023-12/ │ │ ├── _index.md │ │ ├── auction-3.https://v0-122-0--gohugoio.netlify.app/methods/page/data/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/data/The Data method on a Page object returns a unique data object for each page kind. The Data method is only useful within taxonomy and term templates. Themes that are not actively maintained may still use .Data.Pages in list templates. Although that syntax remains functional, use one of these methods instead: Pages, RegularPages, or RegularPagesRecursive The examples that follow are based on this site configuration: hugo. yaml   toml   json   taxonomies: author: authors genre: genres [taxonomies] author = 'authors' genre = 'genres' { "taxonomies": { "author": "authors", "genre": "genres" } } And this content structure:https://v0-122-0--gohugoio.netlify.app/methods/page/date/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/date/Set the date in front matter: content/news/article-1.md yaml   toml   json   --- date: 2023-10-19T00:40:04-07:00 title: Article 1 --- +++ date = 2023-10-19T00:40:04-07:00 title = 'Article 1' +++ { "date": "2023-10-19T00:40:04-07:00", "title": "Article 1" } The date field in front matter is often considered to be the creation date, You can change its meaning, and its effect on your site, in the site configuration. See details. The date is a time.https://v0-122-0--gohugoio.netlify.app/methods/page/description/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/description/Conceptually different that a content summary, a page description is typically used in metadata about the page. content/recipes/sushi.md yaml   toml   json   --- description: Instructions for making spicy tuna hand rolls. title: How to make spicy tuna hand rolls --- +++ description = 'Instructions for making spicy tuna hand rolls.' title = 'How to make spicy tuna hand rolls' +++ { "description": "Instructions for making spicy tuna hand rolls.https://v0-122-0--gohugoio.netlify.app/methods/page/draft/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/draft/By default, Hugo does not publish draft pages when you build your site. To include draft pages when you build your site, use the --buildDrafts command line flag. content/posts/post-1.md yaml   toml   json   --- draft: true title: Post 1 --- +++ draft = true title = 'Post 1' +++ { "draft": true, "title": "Post 1" } {{ .Draft }} → truehttps://v0-122-0--gohugoio.netlify.app/methods/page/eq/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/eq/In this contrived example from a single page template, we list all pages in the current section except for the current page. {{ $currentPage := . }} {{ range .CurrentSection.Pages }} {{ if not (.Eq $currentPage) }} <a href="{{ .RelPermalink }}">{{ .LinkTitle }}</a> {{ end }} {{ end }}https://v0-122-0--gohugoio.netlify.app/methods/page/expirydate/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/expirydate/By default, Hugo excludes expired pages when building your site. To include expired pages, use the --buildExpired command line flag. Set the expiry date in front matter: content/news/article-1.md yaml   toml   json   --- expiryDate: 2024-10-19T00:32:13-07:00 title: Article 1 --- +++ expiryDate = 2024-10-19T00:32:13-07:00 title = 'Article 1' +++ { "expiryDate": "2024-10-19T00:32:13-07:00", "title": "Article 1" } The expiry date is a time.Time value. Format and localize the value with the time.https://v0-122-0--gohugoio.netlify.app/methods/page/file/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/file/By default, not all pages are backed by a file, including top level section pages, taxonomy pages, and term pages. By definition, you cannot retrieve file information when the file does not exist. To back one of the pages above with a file, create an _index.md file in the corresponding directory. For example: content/ └── books/ ├── _index.md <-- the top level section page ├── book-1.md └── book-2.md Code defensively by verifying file existence as shown in each of the examples below.https://v0-122-0--gohugoio.netlify.app/methods/page/firstsection/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/firstsection/A section is a top-level content directory, or any content directory with an _index.md file. When called on the home page, the FirstSection method returns the Page object of the home page itself. Consider this content structure: content/ ├── auctions/ │ ├── 2023-11/ │ │ ├── _index.md <-- first section: auctions │ │ ├── auction-1.md │ │ └── auction-2.md <-- first section: auctions │ ├── 2023-12/ │ │ ├── _index.md │ │ ├── auction-3.https://v0-122-0--gohugoio.netlify.app/methods/page/fragments/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/fragments/New in v0.111.0 In a URL, whether absolute or relative, the fragment links to an id attribute of an HTML element on the page. /articles/article-1#section-2 ------------------- --------- path fragment Hugo assigns an id attribute to each markdown ATX and setext heading within the page content. You can override the id with a markdown attribute as needed. This creates the relationship between an entry in the table of contents (TOC) and a heading on the page.https://v0-122-0--gohugoio.netlify.app/methods/page/fuzzywordcount/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/fuzzywordcount/{{ .FuzzyWordCount }} → 200 To get the exact word count, use the WordCount method.https://v0-122-0--gohugoio.netlify.app/methods/page/getpage/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/getpage/The GetPage method is also available on a Site object. See details. When using the GetPage method on the Page object, specify a path relative to the current directory or relative to the content directory. If Hugo cannot resolve the path to a page, the method returns nil. If the path is ambiguous, Hugo throws an error and fails the build. Consider this content structure: content/ ├── works/ │ ├── paintings/ │ │ ├── _index.https://v0-122-0--gohugoio.netlify.app/methods/page/getterms/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/getterms/Given this front matter: content/books/les-miserables.md yaml   toml   json   --- tags: - historical - classic - fiction title: Les Misérables --- +++ tags = ['historical', 'classic', 'fiction'] title = 'Les Misérables' +++ { "tags": [ "historical", "classic", "fiction" ], "title": "Les Misérables" } This template code: {{ with .GetTerms "tags" }} <p>Tags</p> <ul> {{ range . }} <li><a href="{{ .RelPermalink }}">{{ .LinkTitle }}</a></li> {{ end }} </ul> {{ end }} Is rendered to:https://v0-122-0--gohugoio.netlify.app/methods/page/gitinfo/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/gitinfo/The GitInfo method on a Page object returns an object with additional methods. Hugo’s Git integration is performant, but may increase build times on large sites. Prerequisites Install Git, create a repository, and commit your project files. You must also allow Hugo to access your repository. In your site configuration: hugo. yaml   toml   json   enableGitInfo: true enableGitInfo = true { "enableGitInfo": true } Alternatively, use the command line flag when building your site:https://v0-122-0--gohugoio.netlify.app/methods/page/hasmenucurrent/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/hasmenucurrent/If the page object associated with the menu entry is a section, this method also returns true for any descendant of that section. {{ $currentPage := . }} {{ range site.Menus.main }} {{ if $currentPage.IsMenuCurrent .Menu . }} <a class="active" aria-current="page" href="{{ .URL }}">{{ .Name }}</a> {{ else if $currentPage.HasMenuCurrent .Menu . }} <a class="ancestor" aria-current="true" href="{{ .URL }}">{{ .Name }}</a> {{ else }} <a href="{{ .URL }}">{{ .Name }}</a> {{ end }} {{ end }} See menu templates for a complete example.https://v0-122-0--gohugoio.netlify.app/methods/page/hasshortcode/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/hasshortcode/By example, let’s use MathJax to render a LaTeX mathematical expression: contents/physics/lesson-1.md Albert Einstein’s theory of special relativity expresses the fact that mass and energy are the same physical entity and can be changed into each other. {{< math >}} $$ E=mc^2 $$ {{< /math >}} In the equation, the increased relativistic mass (m) of a body times the speed of light squared (c2) is equal to the kinetic energy (E) of that body.https://v0-122-0--gohugoio.netlify.app/methods/page/headingsfiltered/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/headingsfiltered/Use in conjunction with the Related method on a Pages object. See details.https://v0-122-0--gohugoio.netlify.app/methods/page/insection/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/insection/The InSection method on a page object reports whether the given page is in the given section. Note that the method returns true when comparing a page to a sibling. A section is a top-level content directory, or any content directory with an _index.md file. With this content structure: content/ ├── auctions/ │ ├── 2023-11/ │ │ ├── _index.md │ │ ├── auction-1.md │ │ └── auction-2.md │ ├── 2023-12/ │ │ ├── _index.https://v0-122-0--gohugoio.netlify.app/methods/page/isancestor/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/isancestor/A section is a top-level content directory, or any content directory with an _index.md file. With this content structure: content/ ├── auctions/ │ ├── 2023-11/ │ │ ├── _index.md │ │ ├── auction-1.md │ │ └── auction-2.md │ ├── 2023-12/ │ │ ├── _index.md │ │ ├── auction-3.md │ │ └── auction-4.md │ ├── _index.md │ ├── bidding.md │ └── payment.md └── _index.md When rendering the “auctions” page: {{ with .https://v0-122-0--gohugoio.netlify.app/methods/page/isdescendant/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/isdescendant/A section is a top-level content directory, or any content directory with an _index.md file. With this content structure: content/ ├── auctions/ │ ├── 2023-11/ │ │ ├── _index.md │ │ ├── auction-1.md │ │ └── auction-2.md │ ├── 2023-12/ │ │ ├── _index.md │ │ ├── auction-3.md │ │ └── auction-4.md │ ├── _index.md │ ├── bidding.md │ └── payment.md └── _index.md When rendering the “auctions” page: {{ with .https://v0-122-0--gohugoio.netlify.app/methods/page/ishome/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/ishome/The IsHome method on a Page object returns true if the page kind is home. content/ ├── books/ │ ├── book-1/ │ │ └── index.md <-- kind = page │ ├── book-2.md <-- kind = page │ └── _index.md <-- kind = section └── _index.md <-- kind = home {{ .IsHome }}https://v0-122-0--gohugoio.netlify.app/methods/page/ismenucurrent/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/ismenucurrent/{{ $currentPage := . }} {{ range site.Menus.main }} {{ if $currentPage.IsMenuCurrent .Menu . }} <a class="active" aria-current="page" href="{{ .URL }}">{{ .Name }}</a> {{ else if $currentPage.HasMenuCurrent .Menu . }} <a class="ancestor" aria-current="true" href="{{ .URL }}">{{ .Name }}</a> {{ else }} <a href="{{ .URL }}">{{ .Name }}</a> {{ end }} {{ end }} See menu templates for a complete example.https://v0-122-0--gohugoio.netlify.app/methods/page/isnode/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/isnode/The IsNode method on a Page object returns true if the page kind is home, section, taxonomy, or term. It returns false is the page kind is page. content/ ├── books/ │ ├── book-1/ │ │ └── index.md <-- kind = page, node = false │ ├── book-2.md <-- kind = page, node = false │ └── _index.md <-- kind = section, node = true ├── tags/ │ ├── fiction/ │ │ └── _index.https://v0-122-0--gohugoio.netlify.app/methods/page/ispage/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/ispage/The IsPage method on a Page object returns true if the page kind is page. content/ ├── books/ │ ├── book-1/ │ │ └── index.md <-- kind = page │ ├── book-2.md <-- kind = page │ └── _index.md <-- kind = section └── _index.md <-- kind = home {{ .IsPage }}https://v0-122-0--gohugoio.netlify.app/methods/page/issection/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/issection/The IsSection method on a Page object returns true if the page kind is section. content/ ├── books/ │ ├── book-1/ │ │ └── index.md <-- kind = page │ ├── book-2.md <-- kind = page │ └── _index.md <-- kind = section └── _index.md <-- kind = home {{ .IsSection }}https://v0-122-0--gohugoio.netlify.app/methods/page/istranslated/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/istranslated/With this site configuration: hugo. yaml   toml   json   defaultContentLanguage: en languages: de: contentDir: content/de languageCode: de-DE languageName: Deutsch weight: 2 en: contentDir: content/en languageCode: en-US languageName: English weight: 1 defaultContentLanguage = 'en' [languages] [languages.de] contentDir = 'content/de' languageCode = 'de-DE' languageName = 'Deutsch' weight = 2 [languages.en] contentDir = 'content/en' languageCode = 'en-US' languageName = 'English' weight = 1 { "defaultContentLanguage": "en", "languages": { "de": { "contentDir": "content/de", "languageCode": "de-DE", "languageName": "Deutsch", "weight": 2 }, "en": { "contentDir": "content/en", "languageCode": "en-US", "languageName": "English", "weight": 1 } } } And this content:https://v0-122-0--gohugoio.netlify.app/methods/page/keywords/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/keywords/By default, Hugo evaluates the keywords when creating collections of related content. content/recipes/sushi.md yaml   toml   json   --- keywords: - tuna - sriracha - nori - rice title: How to make spicy tuna hand rolls --- +++ keywords = ['tuna', 'sriracha', 'nori', 'rice'] title = 'How to make spicy tuna hand rolls' +++ { "keywords": [ "tuna", "sriracha", "nori", "rice" ], "title": "How to make spicy tuna hand rolls" } To list the keywords within a template:https://v0-122-0--gohugoio.netlify.app/methods/page/kind/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/kind/The page kind is one of home, page, section, taxonomy, or term. content/ ├── books/ │ ├── book-1/ │ │ └── index.md <-- kind = page │ ├── book-2.md <-- kind = page │ └── _index.md <-- kind = section ├── tags/ │ ├── fiction/ │ │ └── _index.md <-- kind = term │ └── _index.md <-- kind = taxonomy └── _index.md <-- kind = home To get the value within a template:https://v0-122-0--gohugoio.netlify.app/methods/page/language/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/language/The Language method on a Page object returns the language object for the given page. The language object points to the language definition in the site configuration. You can also use the Language method on a Site object. See details. Methods The examples below assume the following in your site configuration: hugo. yaml   toml   json   languages: de: languageCode: de-DE languageDirection: ltr languageName: Deutsch weight: 2 [languages] [languages.de] languageCode = 'de-DE' languageDirection = 'ltr' languageName = 'Deutsch' weight = 2 { "languages": { "de": { "languageCode": "de-DE", "languageDirection": "ltr", "languageName": "Deutsch", "weight": 2 } } } Lang (string) The language tag as defined by RFC 5646.https://v0-122-0--gohugoio.netlify.app/methods/page/lastmod/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/lastmod/Set the last modification date in front matter: content/news/article-1.md yaml   toml   json   --- lastmod: 2023-10-19T00:40:04-07:00 title: Article 1 --- +++ lastmod = 2023-10-19T00:40:04-07:00 title = 'Article 1' +++ { "lastmod": "2023-10-19T00:40:04-07:00", "title": "Article 1" } The last modification date is a time.Time value. Format and localize the value with the time.Format function, or use it with any of the time methods. {{ .Lastmod | time.Format ":date_medium" }} → Oct 19, 2023 In the example above we explicitly set the last modification date in front matter.https://v0-122-0--gohugoio.netlify.app/methods/page/layout/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/layout/Specify the layout field in front matter to target a particular template. See details. content/contact.md. yaml   toml   json   layout: contact title: Contact layout = 'contact' title = 'Contact' { "layout": "contact", "title": "Contact" } Hugo will render the page using contact.html. layouts/ └── _default/ ├── baseof.html ├── contact.html ├── home.html ├── list.html └── single.html Although rarely used within a template, you can access the value with: {{ .https://v0-122-0--gohugoio.netlify.app/methods/page/len/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/len/{{ .Len }} → 42https://v0-122-0--gohugoio.netlify.app/methods/page/linktitle/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/linktitle/The LinkTitle method returns the linkTitle field as defined in front matter, falling back to the value returned by the Title method. content/articles/healthy-desserts.md yaml   toml   json   --- linkTitle: Dessert recipes title: Seventeen delightful recipes for healthy desserts --- +++ linkTitle = 'Dessert recipes' title = 'Seventeen delightful recipes for healthy desserts' +++ { "linkTitle": "Dessert recipes", "title": "Seventeen delightful recipes for healthy desserts" } {{ .LinkTitle }} → Dessert recipes As demonstrated above, defining a link title in front matter is advantageous when the page title is long.https://v0-122-0--gohugoio.netlify.app/methods/page/next/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/next/The behavior of the Prev and Next methods on a Page object is probably the reverse of what you expect. With this content structure: content/ ├── pages/ │ ├── _index.md │ ├── page-1.md <-- front matter: weight = 10 │ ├── page-2.md <-- front matter: weight = 20 │ └── page-3.md <-- front matter: weight = 30 └── _index.md When you visit page-2: The Prev method points to page-3 The Next method points to page-1 Use the opposite label in your navigation links as shown in the example below.https://v0-122-0--gohugoio.netlify.app/methods/page/nextinsection/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/nextinsection/The behavior of the PrevInSection and NextInSection methods on a Page object is probably the reverse of what you expect. With this content structure: content/ ├── books/ │ ├── _index.md │ ├── book-1.md │ ├── book-2.md │ └── book-3.md ├── films/ │ ├── _index.md │ ├── film-1.md │ ├── film-2.md │ └── film-3.md └── _index.md When you visit book-2: The PrevInSection method points to book-3 The NextInSection method points to book-1 Use the opposite label in your navigation links as shown in the example below.https://v0-122-0--gohugoio.netlify.app/methods/page/outputformats/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/outputformats/Hugo generates one or more files per page when building a site. For example, when rendering home, section, taxonomy, and term pages, Hugo generates an HTML file and an RSS file. Both HTML and RSS are built-in output formats. Create multiple output formats, and control generation based on page kind, or by enabling one or more output formats for one or more pages. See details. The OutputFormats method on a Page object returns a slice of OutputFormat objects, each representing one of the output formats enabled for the given page.https://v0-122-0--gohugoio.netlify.app/methods/page/page/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/page/This is a convenience method, useful within partial templates that are called from both shortcodes and page templates. layouts/shortcodes/foo.html {{ partial "my-partial.html" . }} When the shortcode calls the partial, it passes the current context (the dot). The context includes identifiers such as Page, Params, Inner, and Name. layouts/_default/single.html {{ partial "my-partial.html" . }} When the page template calls the partial, it also passes the current context (the dot). But in this case, the dot is the Page object.https://v0-122-0--gohugoio.netlify.app/methods/page/pages/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/pages/The Pages method on a Page object is available to these page kinds: home, section, taxonomy, and term. The templates for these page kinds receive a page collection in context. Range through the page collection in your template: {{ range .Pages.ByTitle }} <h2><a href="{{ .RelPermalink }}">{{ .Title }}</a></h2> {{ end }} Consider this content structure: content/ ├── lessons/ │ ├── lesson-1/ │ │ ├── _index.md │ │ ├── part-1.md │ │ └── part-2.https://v0-122-0--gohugoio.netlify.app/methods/page/paginate/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/paginate/Pagination is the process of splitting a list page into two or more pagers, where each pager contains a subset of the page collection and navigation links to other pagers. By default, the number of elements on each pager is determined by the value of the paginate setting in your site configuration. The default value is 10. Override the value in your site configuration by providing a second argument, an integer, when calling the Paginate method.https://v0-122-0--gohugoio.netlify.app/methods/page/paginator/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/paginator/Pagination is the process of splitting a list page into two or more pagers, where each pager contains a subset of the page collection and navigation links to other pagers. The number of elements on each pager is determined by the value of the paginate setting in your site configuration. The default value is 10. You can invoke pagination on the home page template, section templates, taxonomy templates, and term templates.https://v0-122-0--gohugoio.netlify.app/methods/page/param/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/param/The Param method on a Page object looks for the given KEY in page parameters, and returns the corresponding value. If it cannot find the KEY in page parameters, it looks for the KEY in site parameters. If it cannot find the KEY in either location, the Param method returns nil. Site and theme developers commonly set parameters at the site level, allowing content authors to override those parameters at the page level.https://v0-122-0--gohugoio.netlify.app/methods/page/params/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/params/With this front matter: content/news/annual-conference.md. yaml   toml   json   date: 2023-10-17T15:11:37-07:00 display_related: true params: author: email: jsmith@example.org name: John Smith title: Annual conference date = 2023-10-17T15:11:37-07:00 display_related = true title = 'Annual conference' [params] [params.author] email = 'jsmith@example.org' name = 'John Smith' { "date": "2023-10-17T15:11:37-07:00", "display_related": true, "params": { "author": { "email": "jsmith@example.org", "name": "John Smith" } }, "title": "Annual conference" } The title and date fields are standard parameters—the other fields are user-defined.https://v0-122-0--gohugoio.netlify.app/methods/page/parent/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/parent/A section is a top-level content directory, or any content directory with an _index.md file. The parent section of a regular page is the current section. Consider this content structure: content/ ├── auctions/ │ ├── 2023-11/ │ │ ├── _index.md <-- parent: auctions │ │ ├── auction-1.md │ │ └── auction-2.md <-- parent: 2023-11 │ ├── 2023-12/ │ │ ├── _index.md │ │ ├── auction-3.md │ │ └── auction-4.md │ ├── _index.https://v0-122-0--gohugoio.netlify.app/methods/page/permalink/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/permalink/Site configuration: hugo. yaml   toml   json   baseURL: https://example.org/docs/ title: Documentation baseURL = 'https://example.org/docs/' title = 'Documentation' { "baseURL": "https://example.org/docs/", "title": "Documentation" } Template: {{ $page := .Site.GetPage "/about" }} {{ $page.Permalink }} → https://example.org/docs/about/https://v0-122-0--gohugoio.netlify.app/methods/page/plain/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/plain/The Plain method on a Page object renders markdown and shortcodes to HTML, then strips the HTML tags. It does not strip HTML entities. The plain content does not include front matter. To prevent Go’s html/template package from escaping HTML entities, pass the result through the htmlUnescape function. {{ .Plain | htmlUnescape }}https://v0-122-0--gohugoio.netlify.app/methods/page/plainwords/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/plainwords/The PlainWords method on a Page object calls the Plain method, then uses Go’s strings.Fields function to split the result into words. Fields splits the string s around each instance of one or more consecutive white space characters, as defined by unicode.IsSpace, returning a slice of substrings of s or an empty slice if s contains only white space. As a result, elements within the slice may contain leading or trailing punctuation.https://v0-122-0--gohugoio.netlify.app/methods/page/prev/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/prev/The behavior of the Prev and Next methods on a Page object is probably the reverse of what you expect. With this content structure: content/ ├── pages/ │ ├── _index.md │ ├── page-1.md <-- front matter: weight = 10 │ ├── page-2.md <-- front matter: weight = 20 │ └── page-3.md <-- front matter: weight = 30 └── _index.md When you visit page-2: The Prev method points to page-3 The Next method points to page-1 Use the opposite label in your navigation links as shown in the example below.https://v0-122-0--gohugoio.netlify.app/methods/page/previnsection/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/previnsection/The behavior of the PrevInSection and NextInSection methods on a Page object is probably the reverse of what you expect. With this content structure: content/ ├── books/ │ ├── _index.md │ ├── book-1.md │ ├── book-2.md │ └── book-3.md ├── films/ │ ├── _index.md │ ├── film-1.md │ ├── film-2.md │ └── film-3.md └── _index.md When you visit book-2: The PrevInSection method points to book-3 The NextInSection method points to book-1 Use the opposite label in your navigation links as shown in the example below.https://v0-122-0--gohugoio.netlify.app/methods/page/publishdate/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/publishdate/By default, Hugo excludes pages with future publish dates when building your site. To include future pages, use the --buildFuture command line flag. Set the publish date in front matter: content/news/article-1.md yaml   toml   json   --- publishDate: 2023-10-19T00:40:04-07:00 title: Article 1 --- +++ publishDate = 2023-10-19T00:40:04-07:00 title = 'Article 1' +++ { "publishDate": "2023-10-19T00:40:04-07:00", "title": "Article 1" } The publish date is a time.Time value. Format and localize the value with the time.https://v0-122-0--gohugoio.netlify.app/methods/page/rawcontent/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/rawcontent/The RawContent method on a Page object returns the raw content. The raw content does not include front matter. {{ .RawContent }} This is useful when rendering a page in a plain text output format. Shortcodes within the content are not rendered. To get the raw content with shortcodes rendered, use the RenderShortcodes method on a Page object.https://v0-122-0--gohugoio.netlify.app/methods/page/readingtime/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/readingtime/The estimated reading time is calculated by dividing the number of words in the content by the reading speed. By default, Hugo assumes a reading speed of 212 words per minute. For CJK languages, it assumes 500 words per minute. {{ printf "Estimated reading time: %d minutes" .ReadingTime }} Reading speed varies by language. Create language-specific estimated reading times on your multilingual site using site parameters. hugo. yaml   toml   json   languages: de: contentDir: content/de languageCode: de-DE languageName: Deutsch params: reading_speed: 179 weight: 2 en: contentDir: content/en languageCode: en-US languageName: English params: reading_speed: 228 weight: 1 [languages] [languages.https://v0-122-0--gohugoio.netlify.app/methods/page/ref/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/ref/The map of option contains: path (string) The path to the page, relative to the content directory. Required. lang (string) The language (site) to search for the page. Default is the current language. Optional. outputFormat (string) The output format to search for the page. Default is the current output format. Optional. The examples below show the rendered output when visiting a page on the English language version of the site:https://v0-122-0--gohugoio.netlify.app/methods/page/regularpages/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/regularpages/The RegularPages method on a Page object is available to these page kinds: home, section, taxonomy, and term. The templates for these page kinds receive a page collection in context. Range through the page collection in your template: {{ range .RegularPages.ByTitle }} <h2><a href="{{ .RelPermalink }}">{{ .Title }}</a></h2> {{ end }} Consider this content structure: content/ ├── lessons/ │ ├── lesson-1/ │ │ ├── _index.md │ │ ├── part-1.md │ │ └── part-2.https://v0-122-0--gohugoio.netlify.app/methods/page/regularpagesrecursive/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/regularpagesrecursive/The RegularPagesRecursive method on a Page object is available to these page kinds: home, section, taxonomy, and term. The templates for these page kinds receive a page collection in context. Range through the page collection in your template: {{ range .RegularPagesRecursive.ByTitle }} <h2><a href="{{ .RelPermalink }}">{{ .Title }}</a></h2> {{ end }} Consider this content structure: content/ ├── lessons/ │ ├── lesson-1/ │ │ ├── _index.md │ │ ├── part-1.md │ │ └── part-2.https://v0-122-0--gohugoio.netlify.app/methods/page/relpermalink/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/relpermalink/Site configuration: hugo. yaml   toml   json   baseURL: https://example.org/docs/ title: Documentation baseURL = 'https://example.org/docs/' title = 'Documentation' { "baseURL": "https://example.org/docs/", "title": "Documentation" } Template: {{ $page := .Site.GetPage "/about" }} {{ $page.RelPermalink }} → /docs/about/https://v0-122-0--gohugoio.netlify.app/methods/page/relref/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/relref/The map of option contains: path (string) The path to the page, relative to the content directory. Required. lang (string) The language (site) to search for the page. Default is the current language. Optional. outputFormat (string) The output format to search for the page. Default is the current output format. Optional. The examples below show the rendered output when visiting a page on the English language version of the site:https://v0-122-0--gohugoio.netlify.app/methods/page/render/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/render/Typically used when ranging over a page collection, the Render method on a Page object renders the given template, passing the given page as context. {{ range site.RegularPages }} <h2><a href="{{ .RelPermalink }}">{{ .LinkTitle }}</a></h2> {{ .Render "summary" }} {{ end }} In the example above, note that the template (“summary”) is identified by its file name without directory or extension. Although similar to the partial function, there are key differences.https://v0-122-0--gohugoio.netlify.app/methods/page/rendershortcodes/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/rendershortcodes/New in v0.117.0 Use this method in shortcode templates to compose a page from multiple content files, while preserving a global context for footnotes and the table of contents. For example: layouts/shortcodes/include.html {{ $p := site.GetPage (.Get 0) }} {{ $p.RenderShortcodes }} Then in your markdown: content/about.md {{% include "/snippets/services.md" %}} {{% include "/snippets/values.md" %}} {{% include "/snippets/leadership.md" %}} Each of the included markdown files can contain calls to other shortcodes.https://v0-122-0--gohugoio.netlify.app/methods/page/renderstring/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/renderstring/{{ $s := "An *emphasized* word" }} {{ $s | .RenderString }} → An <em>emphasized</em> word This method takes an optional map of options: display (string) Specify either inline or block. If inline, removes surrounding p tags from short snippets. Default is inline. markup (string) Specify a markup identifier for the provided markup. Default is the markup front matter value, falling back to the value derived from the page’s file extension.https://v0-122-0--gohugoio.netlify.app/methods/page/resources/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/resources/The Resources method on a Page object returns a collection of page resources. A page resource is a file within a page bundle. To work with global or remote resources, see the resources functions. Methods ByType (resource.Resources) Returns a collection of page resources of the given media type, or nil if none found. The media type is typically one of image, text, audio, video, or application. {{ range .Resources.ByType "image" }} <img src="{{ .https://v0-122-0--gohugoio.netlify.app/methods/page/scratch/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/scratch/The Scratch method on a Page object creates a scratch pad to store and manipulate data. To create a scratch pad that is not reset on server rebuilds, use the Store method instead. To create a locally scoped scratch pad that is not attached to a Page object, use the newScratch function. Methods Set Sets the value of a given key. {{ .Scratch.Set "greeting" "Hello" }} Get Gets the value of a given key.https://v0-122-0--gohugoio.netlify.app/methods/page/section/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/section/With this content structure: content/ ├── lessons/ │ ├── math/ │ │ ├── _index.md │ │ ├── lesson-1.md │ │ └── lesson-2.md │ └── _index.md └── _index.md When rendering lesson-1.md: {{ .Section }} → lessons In the example above “lessons” is the top level section. The Section method is often used with the where function to build a page collection. {{ range where .Site.RegularPages "Section" "lessons" }} <h2><a href="{{ .RelPermalink }}">{{ .https://v0-122-0--gohugoio.netlify.app/methods/page/sections/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/sections/A section is a top-level content directory, or any content directory with an _index.md file. With this content structure: content/ ├── auctions/ │ ├── 2023-11/ │ │ ├── _index.md <-- front matter: weight = 202311 │ │ ├── auction-1.md │ │ └── auction-2.md │ ├── 2023-12/ │ │ ├── _index.md <-- front matter: weight = 202312 │ │ ├── auction-3.md │ │ └── auction-4.md │ ├── _index.md <-- front matter: weight = 30 │ ├── bidding.https://v0-122-0--gohugoio.netlify.app/methods/page/site/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/site/See Site methods. {{ .Site.Title }}https://v0-122-0--gohugoio.netlify.app/methods/page/sitemap/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/sitemap/Access to the Sitemap method on a Page object is restricted to sitemap templates. Methods ChangeFreq (string) How frequently a page is likely to change. Valid values are always, hourly, daily, weekly, monthly, yearly, and never. Default is "" (change frequency omitted from rendered sitemap). {{ .Sitemap.ChangeFreq }} Priority (float) The priority of a page relative to any other page on the site. Valid values range from 0.0 to 1.0. Default is -1 (priority omitted from rendered sitemap).https://v0-122-0--gohugoio.netlify.app/methods/page/sites/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/sites/This is a convenience method to access .Site.Sites. With this site configuration: hugo. yaml   toml   json   defaultContentLanguage: de defaultContentLanguageInSubdir: false languages: de: languageCode: de-DE languageDirection: ltr languageName: Deutsch title: Projekt Dokumentation weight: 1 en: languageCode: en-US languageDirection: ltr languageName: English title: Project Documentation weight: 2 defaultContentLanguage = 'de' defaultContentLanguageInSubdir = false [languages] [languages.de] languageCode = 'de-DE' languageDirection = 'ltr' languageName = 'Deutsch' title = 'Projekt Dokumentation' weight = 1 [languages.https://v0-122-0--gohugoio.netlify.app/methods/page/slug/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/slug/ content/recipes/spicy-tuna-hand-rolls.md yaml   toml   json   --- slug: sushi title: How to make spicy tuna hand rolls --- +++ slug = 'sushi' title = 'How to make spicy tuna hand rolls' +++ { "slug": "sushi", "title": "How to make spicy tuna hand rolls" } This page will be served from: https://example.org/recipes/sushi To get the slug value within a template: {{ .Slug }} → sushihttps://v0-122-0--gohugoio.netlify.app/methods/page/store/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/store/The Store method on a Page object creates a persistent scratch pad to store and manipulate data. In contrast with the Scratch method, the scratch pad created by the Store method is not reset on server rebuilds. To create a locally scoped scratch pad that is not attached to a Page object, use the newScratch function. Methods Set Sets the value of a given key. {{ .Store.Set "greeting" "Hello" }} Get Gets the value of a given key.https://v0-122-0--gohugoio.netlify.app/methods/page/summary/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/summary/There are three ways to define the content summary: Let Hugo create the summary based on the first 70 words. You can change the number of words by setting the summaryLength in your site configuration. Manually split the content with a <--more--> tag in markdown. Everything before the tag is included in the summary. Create a summary field in front matter. To list the pages in a section with a summary beneath each link:https://v0-122-0--gohugoio.netlify.app/methods/page/tableofcontents/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/tableofcontents/The TableOfContents method on a Page object returns an ordered or unordered list of the markdown ATX and setext headings within the page content. This template code: {{ .TableOfContents }} Produces this HTML: <nav id="TableOfContents"> <ul> <li><a href="#section-1">Section 1</a> <ul> <li><a href="#section-11">Section 1.1</a></li> <li><a href="#section-12">Section 1.2</a></li> </ul> </li> <li><a href="#section-2">Section 2</a></li> </ul> </nav> By default, the TableOfContents method returns an unordered list of level 2 and level 3 headings. You can adjust this in your site configuration:https://v0-122-0--gohugoio.netlify.app/methods/page/title/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/title/With pages backed by a file, the Title method returns the title field as defined in front matter: content/about.md yaml   toml   json   --- title: About us --- +++ title = 'About us' +++ { "title": "About us" } {{ .Title }} → About us With section pages not backed by a file, the Title method returns the section name, pluralized and converted to title case. To disable pluralization:https://v0-122-0--gohugoio.netlify.app/methods/page/translationkey/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/translationkey/The translation key creates a relationship between all translations of a given page. The translation key is derived from the file path, or from the translationKey parameter if defined in front matter. With this site configuration: hugo. yaml   toml   json   defaultContentLanguage: en languages: de: contentDir: content/de languageCode: de-DE languageName: Deutsch weight: 2 en: contentDir: content/en languageCode: en-US languageName: English weight: 1 defaultContentLanguage = 'en' [languages] [languages.de] contentDir = 'content/de' languageCode = 'de-DE' languageName = 'Deutsch' weight = 2 [languages.https://v0-122-0--gohugoio.netlify.app/methods/page/translations/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/translations/With this site configuration: hugo. yaml   toml   json   defaultContentLanguage: en languages: de: contentDir: content/de languageCode: de-DE languageName: Deutsch weight: 2 en: contentDir: content/en languageCode: en-US languageName: English weight: 1 fr: contentDir: content/fr languageCode: fr-FR languageName: Français weight: 3 defaultContentLanguage = 'en' [languages] [languages.de] contentDir = 'content/de' languageCode = 'de-DE' languageName = 'Deutsch' weight = 2 [languages.en] contentDir = 'content/en' languageCode = 'en-US' languageName = 'English' weight = 1 [languages.https://v0-122-0--gohugoio.netlify.app/methods/page/truncated/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/truncated/There are three ways to define the content summary: Let Hugo create the summary based on the first 70 words. You can change the number of words by setting the summaryLength in your site configuration. Manually split the content with a <--more--> tag in markdown. Everything before the tag is included in the summary. Create a summary field in front matter. The Truncated method returns false if you define the summary in front matter.https://v0-122-0--gohugoio.netlify.app/methods/page/type/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/type/The Type method on a Page object returns the content type of the given page. The content type is defined by the type field in front matter, or inferred from the top-level directory name if the type field in front matter is not defined. With this content structure: content/ ├── auction/ │ ├── _index.md │ ├── item-1.md │ └── item-2.md <-- front matter: type = books ├── books/ │ ├── _index.https://v0-122-0--gohugoio.netlify.app/methods/page/weight/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/weight/The Weight method on a Page object returns the weight of the given page as defined in front matter. content/recipes/sushi.md yaml   toml   json   --- title: How to make spicy tuna hand rolls weight: 42 --- +++ title = 'How to make spicy tuna hand rolls' weight = 42 +++ { "title": "How to make spicy tuna hand rolls", "weight": 42 } Page weight controls the position of a page within a collection that is sorted by weight.https://v0-122-0--gohugoio.netlify.app/methods/page/wordcount/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/methods/page/wordcount/{{ .WordCount }} → 103 To round up to nearest multiple of 100, use the FuzzyWordCount method.