<!--more--> at the appropriate place in the content page. See [Summaries](/content/summaries/) for more details.
* `.TableOfContents` The rendered [table of contents](/content-management/table-of-contents/) for the page.
* `.Title` The title for this page.
* `.Translations` A list of translated versions of the current page. See [Multilingual](/content-management/multilingual-mode/) for more info.
* `.Truncated` A boolean, `true` if the `.Summary` is truncated. Useful for showing a "Read more..." link only if necessary. See [Summaries](/content/summaries/) for more details.
* `.Type` The [content type][] (e.g., `post`).
* `.URL` The relative URL for this page. Note that if `URL` is set directly in front matter, that URL is returned as-is.
* `.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.
## Page-level Params
Any other value defined in the front matter, including taxonomies, will be made available as part of the `.Params variable.
For example, the *tags* and *categories* taxonomies are accessed with:
* `.Params.tags`
* `.Params.categories`
{{% note "Casing of Params" %}}
Page-level `.Params` are *only* accessible in lowercase.
{{% /note %}}
This is particularly useful for the introduction of user-defined fields in content files. For example, a Hugo website on book reviews could have the following front matter in `/content/review/book01.md`:
```yaml
---
...
affiliatelink: "http://www.my-book-link.here"
recommendedby: "My Mother"
---
```
Which would then be accessible to a template at `/themes/yourtheme/layouts/review/single.html` through `.Params.affiliatelink` and `.Params.recommendedby`, respectively. Two common situations where these could be introduced are as a value of a certain attribute (like `href=""` below) or by itself to be displayed. Sample syntaxes include:
```html
It was recommended by {{ .Params.recommendedby }}.
``` which would render ```htmlIt was recommended by my Mother.
``` {{% note %}} See [Archetypes](/content-management/archetyps) for consistency of `Params` across pieces of content. {{% /note %}} ### Param method In Hugo, you can declare params both for the site and the individual page. A common use case is to have a general value for the site and a more specific value for some of the pages (i.e., a header image): ```golang {{ $.Param "header_image" }} ``` The `.Param` method provides a way to resolve a single value whether it's in a page parameter or a site parameter. When front matter contains nested fields like the following: ```yaml --- author: given_name: John family_name: Feminella display_name: John Feminella --- ``` `.Param` can access them 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`: ```golang {{ $.Param "favorites.flavor" }} ``` [content type]: /content-management/content-types/ [crossreferences]: /content-management/cross-references/ [hugovariables]: /variables-and-params/hugo-variables/ [sitevariables]: /variables-and-params/site-variables/