glossary: More edits

2026-08-25 07:48:52 +00:00 · 2025-02-02 14:09:19 -08:00
parent 1f0c54e608
commit 612b8528f9
91 changed files with 124 additions and 103 deletions
@@ -68,6 +68,7 @@
    "# ----------------------------------------------------------------------",
    "# cspell: ignore hugo terminology",
    "# ----------------------------------------------------------------------",
+    "alignx",
    "attrlink",
    "canonify",
    "codeowners",
@@ -85,6 +86,7 @@
    "stringifier",
    "struct",
    "toclevels",
+    "unmarshal",
    "unpublishdate",
    "zgotmplz",
    "# ----------------------------------------------------------------------",
@@ -158,6 +160,8 @@
    "# cspell: ignore miscellaneous",
    "# ----------------------------------------------------------------------",
    "achristie",
+    "ccpa",
+    "crpa",
    "ddmaurier",
    "dring",
    "fleqn",
@@ -171,6 +175,7 @@
    "rsmith",
    "tdewolff",
    "tjones",
+    "vcard",
    "wcag",
    "xfeff"
  ]
@@ -2,4 +2,4 @@
 title: action
 ---

-See [template action](g).
+See [_template action_](g).
@@ -1,5 +1,6 @@
 ---
 title: array
+reference: https://go.dev/ref/spec#Array_types
 ---

 An _array_ is a numbered sequence of [_elements_](g). Unlike Go's [_slice_](g) data type, an array has a fixed length. Elements within an array can be [_scalars_](g), slices, [_maps_](g), pages, or other arrays.
@@ -2,4 +2,4 @@
 title: bool
 ---

-See [boolean](g).
+See [_boolean_](g).
@@ -2,4 +2,4 @@
 title: chain
 ---

-Within a template, to connect one or more [identifiers](g) with a dot. An identifier can represent a method, object, or field. For example, `.Site.Params.author.name` or `.Date.UTC.Hour`.
+To _chain_ is to connect one or more [_identifiers_](g) with a dot. An identifier can represent a [_method_](g), [_object_](g), or [_field_](g). For example, `.Site.Params.author.name` or `.Date.UTC.Hour`.
@@ -2,4 +2,4 @@
 title: CJK
 ---

-A collective term for the Chinese, Japanese, and Korean languages.
+_CJK_ is a collective term for the Chinese, Japanese, and Korean languages.
@@ -2,4 +2,4 @@
 title: CLI
 ---

-Command line interface.
+_CLI_ is an abbreviation of Command Line Interface.
@@ -2,4 +2,4 @@
 title: collection
 ---

-An [array](g), [slice](g), or [map](g).
+A _collection_ is an [_array_](g), [_slice_](g), or [_map_](g).
@@ -3,4 +3,4 @@ title: content adapter
 reference: /content-management/content-adapters
 ---

-A template that dynamically creates pages when building a site. For example, use a content adapter to create pages from a remote data source such as JSON, TOML, YAML, or XML.
+A _content adapter_ is a template that dynamically creates pages when building a site. For example, use a content adapter to create pages from a remote data source such as JSON, TOML, YAML, or XML.
@@ -3,4 +3,4 @@ title: content format
 reference: /content-management/formats
 ---

-A markup language for creating content. Typically Markdown, but may also be HTML, AsciiDoc, Org, Pandoc, or reStructuredText.
+A _content format_ is a markup language for creating content. Typically Markdown, but may also be HTML, AsciiDoc, Org, Pandoc, or reStructuredText.
@@ -3,4 +3,4 @@ title: content type
 reference: /content-management/types
 ---

-A classification of content inferred from the top-level directory name or the `type` set in [front matter](g). Pages in the root of the `content` directory, including the home page, are of type "page". Accessed via `.Page.Type` in [templates](g).
+A _content type_ is a classification of content inferred from the top-level directory name or the `type` set in [front matter](g). Pages in the root of the `content` directory, including the home page, are of type "page". Accessed via `.Page.Type` in [_templates_](g).
@@ -3,4 +3,4 @@ title: content view
 reference: /templates/content-view
 ---

-A template called with the `.Page.Render` method.
+A _content view_ is a template called with the [`Render`](/methods/page/render/) method on a `Page` object.
@@ -3,4 +3,4 @@ title: context
 reference: /templates/introduction/#context
 ---

-Represented by a dot "." within a [template action](g), context is the current location in a data structure. For example, while iterating over a [collection](g) of pages, the context within each iteration is the page's data structure. The context received by each template depends on template type and/or how it was called.
+Represented by a dot "." within a [_template action_](g), _context_ is the current location in a data structure. For example, while iterating over a [_collection_](g) of pages, the context within each iteration is the page's data structure. The context received by each template depends on template type and/or how it was called.
@@ -2,4 +2,4 @@
 title: default sort order
 ---

-The default sort order for page collections. Hugo sorts by [weight](g), then by date (descending), then by link title, and then by file path.
+The _default sort order_ is the default order in which Hugo sorts page collections: by [_weight_](g), then by date (descending), then by link title, and then by file path.
@@ -2,4 +2,4 @@
 title: embedded template
 ---

-An _embedded template_ is a built-in component within the Hugo application. This includes features like [partials](g), [shortcodes](g), and [render hooks](g) that provide pre-defined structures or functionalities for creating website content.
+An _embedded template_ is a built-in component within the Hugo application. This includes features like [_partials_](g), [_shortcodes_](g), and [_render hooks_](g) that provide pre-defined structures or functionalities for creating website content.
@@ -2,7 +2,7 @@
 title: environment
 ---

-Typically one of `development`, `staging`, or `production`, each environment may exhibit different behavior depending on configuration and template logic. For example, in a production environment you might minify and fingerprint CSS, but that probably doesn't make sense in a development environment.
+Typically one of `development`, `staging`, or `production`, each _environment_ may exhibit different behavior depending on configuration and template logic. For example, in a production environment you might minify and fingerprint CSS, but that probably doesn't make sense in a development environment.

 When running the built-in development server with the `hugo server` command, the environment is set to `development`. When building your site with the `hugo` command, the environment is set to `production`. To override the environment value, use the `--environment` command line flag or the `HUGO_ENVIRONMENT` environment variable.

@@ -3,4 +3,4 @@ title: flag
 reference: /commands/hugo
 ---

-An option passed to a command-line program, beginning with one or two hyphens.
+A _flag_ is an option passed to a command-line program, beginning with one or two hyphens.
@@ -2,4 +2,4 @@
 title: floating point
 ---

-A numeric data type with a fractional component. For example, `3.14159`.
+The term _floating point_ refers to a numeric data type with a fractional component. For example, `3.14159`.
@@ -2,4 +2,4 @@
 title: fragment
 ---

-The final segment of a URL, beginning with a hash (`#`) mark, that references an `id` attribute of an HTML element on the page.
+A _fragment_ is the final segment of a URL, beginning with a hash (`#`) mark, that references an `id` attribute of an HTML element on the page.
@@ -3,4 +3,4 @@ title: front matter
 reference: /content-management/front-matter
 ---

-Metadata at the beginning of each content page, separated from the content by format-specific delimiters.
+The term _front matter_ refers to the metadata at the beginning of each content page, separated from the content by format-specific delimiters.
@@ -3,4 +3,4 @@ title: function
 reference: /functions
 ---

-Used within a [template action](g), a function takes one or more [arguments](g) and returns a value. Unlike [methods](g), functions are not associated with an [object](g). 
+Used within a [_template action_](g), a _function_ takes one or more [_arguments_](g) and returns a value. Unlike [_methods_](g), functions are not associated with an [_object_](g).
@@ -2,9 +2,4 @@
 title: global resource
 ---

-A file within the `assets` directory, or within any directory mounted to the `assets` directory. Capture one or more global resources using the [`resources.Get`], [`resources.GetMatch`], [`resources.Match`], or [`resources.ByType`] functions.
-
-[`resources.Get`]: /functions/resources/get/
-[`resources.GetMatch`]: /functions/resources/getmatch/
-[`resources.Match`]: /functions/resources/match/
-[`resources.ByType`]: /functions/resources/byType/
+A _global resource_ is file within the `assets` directory, or within any directory mounted to the `assets` directory.
@@ -1,5 +1,6 @@
 ---
 title: headless bundle
+reference: /content-management/build-options/
 ---

-An unpublished leaf or branch bundle whose content and resources you can include in other pages. See [build options](/content-management/build-options/).
+A _headless bundle_ is an unpublished leaf or branch bundle whose content and resources you can include in other pages.
@@ -0,0 +1,5 @@
+---
+title: i18n
+---
+
+See [_internationalization_](g).
@@ -2,4 +2,4 @@
 title: identifier
 ---

-A string that represents a variable, method, object, or field. It must conform to Go's [language specification](https://go.dev/ref/spec#Identifiers), beginning with a letter or underscore, followed by zero or more letters, digits, or underscores.
+An _identifier_ is a string that represents a variable, method, object, or field. It must conform to Go's [language specification](https://go.dev/ref/spec#Identifiers), beginning with a letter or underscore, followed by zero or more letters, digits, or underscores.
@@ -2,4 +2,4 @@
 title: int
 ---

-See [integer](g).
+See [_integer_](g).
@@ -2,4 +2,4 @@
 title: integer
 ---

-A numeric data type without a fractional component. For example, `42`.
+An _integer_ is a numeric data type without a fractional component. For example, `42`.
@@ -2,4 +2,4 @@
 title: internationalization
 ---

-Software design and development efforts that enable [localization](g). See the [W3C definition](https://www.w3.org/International/questions/qa-i18n). Abbreviated i18n.
+The term _internationalization_ refers to software design and development efforts that enable [_localization_](g).
@@ -1,5 +1,6 @@
 ---
 title: interpreted string literal
+reference: https://go.dev/ref/spec#String_literals
 ---

-An _interpreted string literal_ is a character sequences between double quotes, as in "foo". Within the quotes, any character may appear except a newline and an unescaped double quote. The text between the quotes forms the value of the literal, with backslash escapes interpreted. See&nbsp;[details](https://go.dev/ref/spec#String_literals).
+An _interpreted string literal_ is a character sequences between double quotes, as in "foo". Within the quotes, any character may appear except a newline and an unescaped double quote. The text between the quotes forms the value of the literal, with backslash escapes interpreted.
@@ -2,10 +2,10 @@
 title: interval
 ---

-An [interval](https://en.wikipedia.org/wiki/Interval_(mathematics)) is a range of numbers between two endpoints: closed, open, or half-open.
+An [_interval_](https://en.wikipedia.org/wiki/Interval_(mathematics)) is a range of numbers between two endpoints: closed, open, or half-open.

- A _closed_ interval, denoted by brackets, includes its endpoints. For example, [0,&nbsp;1]&nbsp;is the interval where `0 <= x <= 1`.
+- A _closed interval_, denoted by brackets, includes its endpoints. For example, [0,&nbsp;1]&nbsp;is the interval where `0 <= x <= 1`.

- An _open_ interval, denoted by parentheses, excludes its endpoints. For example, (0,&nbsp;1)&nbsp;is the interval where `0 < x < 1`.
+- An _open interval_, denoted by parentheses, excludes its endpoints. For example, (0,&nbsp;1)&nbsp;is the interval where `0 < x < 1`.

- A _half-open_ interval includes only one of its endpoints. For example, (0,&nbsp;1]&nbsp;is the _left-open_ interval where `0 < x <= 1`, while [0,&nbsp;1)&nbsp;is the _right-open_ interval where `0 <= x < 1`.
+- A _half-open interval_ includes only one of its endpoints. For example, (0,&nbsp;1]&nbsp;is the _left-open_ interval where `0 < x <= 1`, while [0,&nbsp;1)&nbsp;is the _right-open_ interval where `0 <= x < 1`.
@@ -2,4 +2,4 @@
 title: kind
 ---

-See [page kind](g).
+See [_page kind_](g).
@@ -0,0 +1,5 @@
+---
+title: l10n
+---
+
+See [_localization_](g).
@@ -2,4 +2,4 @@
 title: layout
 ---

-See [template](g).
+See [_template_](g).
@@ -1,5 +1,6 @@
 ---
 title: leaf bundle
+reference: /content-management/page-bundles/
 ---

-A directory that contains an&nbsp;`index.md`&nbsp;file and zero or more [resources](g). Analogous to a physical leaf, a leaf bundle is at the end of a branch. It has no descendants. See&nbsp;[details](/content-management/page-bundles/).
+A _leaf bundle_ is a directory that contains an&nbsp;`index.md`&nbsp;file and zero or more [_resources_](g). Analogous to a physical leaf, a leaf bundle is at the end of a branch. It has no descendants.
@@ -2,4 +2,4 @@
 title: lexer
 ---

-A software component that identifies keywords, identifiers, operators, numbers, and other basic building blocks of a programming language within the input text.
+A _lexer_ is a software component that identifies keywords, identifiers, operators, numbers, and other basic building blocks of a programming language within the input text.
@@ -2,4 +2,4 @@
 title: list page
 ---

-Any [page kind](g) that receives a page [collection](g) in [context](g). This includes the home page, [section pages](g), [taxonomy pages](g), and [term pages](g).
+A list page is any [_page kind_](g) that receives a page [_collection_](g) in [_context_](g). This includes the home page, [section pages](g), [taxonomy pages](g), and [term pages](g).
@@ -2,4 +2,4 @@
 title: list template
 ---

-Any template that renders a [list page](g). This includes [home](/templates/types/#home), [section](/templates/types/#section), [taxonomy](/templates/types/#taxonomy), and [term](/templates/types/#term) templates.
+A _list template_ is any [_template_](g) that renders a [_list page_](g). This includes home, [_section_](g), [_taxonomy_](g), and [_term_](g) templates.
@@ -1,5 +1,6 @@
 ---
 title: localization
+reference: /content-management/multilingual/
 ---

-Adaptation of a site to meet language and regional requirements. This includes translations, language-specific media, date and currency formats, etc. See&nbsp;[details](/content-management/multilingual/) and the [W3C definition](https://www.w3.org/International/questions/qa-i18n). Abbreviated l10n.
+The term _localization_ refers to the process of adapting a site to meet language and regional requirements. This includes translations, date formats, number formats, currency formats, and collation order.
@@ -1,7 +1,8 @@
 ---
 title: logical path
+reference: /methods/page/path/#examples
 ---

 {{< new-in 0.123.0 />}}

-A page or page resource identifier derived from the file path, excluding its extension and language identifier. This value is neither a file path nor a URL. Starting with a file path relative to the `content` directory, Hugo determines the logical path by stripping the file extension and language identifier, converting to lower case, then replacing spaces with hyphens. See [examples](/methods/page/path/#examples).
+A _logical path_ is a page or page resource identifier derived from the file path, excluding its extension and language identifier. This value is neither a file path nor a URL. Starting with a file path relative to the `content` directory, Hugo determines the logical path by stripping the file extension and language identifier, converting to lower case, then replacing spaces with hyphens.
@@ -1,5 +1,6 @@
 ---
 title: map
+reference: https://go.dev/ref/spec#Map_types
 ---

-An unordered group of elements, each indexed by a unique key. See the [Go&nbsp;documentation](https://go.dev/ref/spec#Map_types) for details.
+A _map_ is an unordered group of elements, each indexed by a unique key.
@@ -3,4 +3,4 @@ title: Markdown attribute
 reference: /content-management/markdown-attributes/
 ---

-A list of attributes, containing one or more key-value pairs, separated by spaces or commas, and wrapped by braces. Apply Markdown attributes to images and block-level elements including blockquotes, fenced code blocks, headings, horizontal rules, lists, paragraphs, and tables.
+A _Markdown attribute_ is a key-value pair attached to a Markdown element.  These attributes are commonly used to add HTML attributes, like `class` and `id`, to the element when it's rendered into HTML.  They provide a way to extend the basic Markdown syntax and add more semantic meaning or styling hooks to your content.
@@ -1,5 +1,6 @@
 ---
 title: marshal
+reference: /functions/transform/remarshal/
 ---

-To transform a data structure into a serialized object. For example, transforming a [map](g) into a JSON string. See [unmarshal](g).
+To _marshal_ is to transform a data structure into a serialized object. For example, transforming a [_map_](g) into a JSON string.
@@ -2,4 +2,4 @@
 title: method
 ---

-Used within a [template action](g) and associated with an [object](g), a method takes zero or more [arguments](g) and either returns a value or performs an action. For example, `.IsHome` is a method on the `.Page` object which returns `true` if the current page is the home page. See also [function](g).
+Used within a [_template action_](g) and associated with an [_object_](g), a _method_ takes zero or more [_arguments_](g) and either returns a value or performs an action. For example, `.IsHome` is a method on the `.Page` object which returns `true` if the current page is the home page. See also [_function_](g).
@@ -1,5 +1,6 @@
 ---
 title: module
+reference: /hugo-modules/
 ---

-Like a [theme](g), a module is a packaged combination of [archetypes](g), assets, content, data, [templates](g), translation tables, static files, or configuration settings. A module may serve as the basis for a new site, or to augment an existing site. See&nbsp;[details](/hugo-modules/).
+A _module_ is a packaged combination of [_archetypes_](g), assets, content, data, [_templates_](g), translation tables, static files, or configuration settings. A module may serve as the basis for a new site, or to augment an existing site.
@@ -2,4 +2,4 @@
 title: node
 ---

-A class of [page kinds](g) including `home`, `section`, `taxonomy`, and `term`.
+A _node_ is a class of [_page kinds_](g) including `home`, `section`, `taxonomy`, and `term`.
@@ -2,4 +2,4 @@
 title: object
 ---

-A data structure with or without associated [methods](g).
+An _object_ is a data structure with or without associated [_methods_](g).
@@ -2,7 +2,7 @@
 title: ordered taxonomy
 ---

-Created by invoking the [`Alphabetical`] or [`ByCount`] method on a [`Taxonomy`](g) object, which is a [map](g), an _ordered taxonomy_ is a [slice](g), where each element is an object that contains the [term](g) and a slice of its [weighted pages](g).
+Created by invoking the [`Alphabetical`] or [`ByCount`] method on a [`Taxonomy`](g) object, which is a [_map_](g), an _ordered taxonomy_ is a [_slice_](g), where each element is an object that contains the [_term_](g) and a slice of its [weighted pages](g).

 [`Alphabetical`]: /methods/taxonomy/alphabetical/
 [`ByCount`]: /methods/taxonomy/bycount/
@@ -1,7 +1,6 @@
 ---
 title: output format
+reference: /templates/output-formats/
 ---

-Hugo generates one or more files per page when building a site. For example, when rendering home, [section](g), [taxonomy](g), and [term](g) 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](g), or by enabling one or more output formats for one or more pages. See&nbsp;[details].
-
-[details]: /templates/output-formats/
+An _output format_ is a collection of settings that defines how Hugo renders a file when building a site. For example, `html`, `rss`, and `json` are built-in output formats. You can create multiple output formats and control their generation based on [page kind](g), or by enabling one or more output formats for specific pages.
@@ -1,5 +1,6 @@
 ---
 title: page bundle
+reference: /content-management/page-bundles/
 ---

-A directory that encapsulates both content and associated [resources](g). There are two types of page bundles: [leaf bundles](g) and [branch bundles](g). See&nbsp;[details](/content-management/page-bundles/).
+A _page bundle_ is a directory that encapsulates both content and associated [_resources_](g). There are two types of page bundles: [_leaf bundles_](g) and [_branch bundles_](g).
@@ -2,4 +2,4 @@
 title: page collection
 ---

-A slice of `Page` objects.
+A _page collection_ is a slice of `Page` objects.
@@ -1,7 +1,6 @@
 ---
 title: page kind
+reference: /methods/page/kind/
 ---

-A classification of pages, one of `home`, `page`, `section`, `taxonomy`, or `term`. See&nbsp;[details](/methods/page/kind/).
-
-Note that there are also `RSS`, `sitemap`, `robotsTXT`, and `404` page kinds, but these are only available during the rendering of each of these respective page's kind and therefore *not* available in any of the `Pages` collections.
+A _page kind_ is a classification of pages, one of `home`, `page`, `section`, `taxonomy`, or `term`.
@@ -2,6 +2,4 @@
 title: page resource
 ---

-A file within a [page bundle](g). Capture one or more page resources using any of the [`Resources`] methods on a `Page` object.
-
-[`Resources`]: /methods/page/resources/#methods
+A _page resource_ is a file within a [_page bundle_](g).
@@ -2,4 +2,4 @@
 title: pager
 ---

-Created during [pagination](g), a pager contains a subset of a list page and navigation links to other pagers.
+Created during [_pagination_](g), a _pager_ contains a subset of a list page and navigation links to other pagers.
@@ -2,4 +2,4 @@
 title: paginate
 ---

-To split a list page into two or more subsets.
+To _paginate_ is to split a list page into two or more subsets.
@@ -3,4 +3,4 @@ title: pagination
 reference: /templates/pagination
 ---

-The process of [paginating](g) a list page.
+The term _pagination_ refers to the process of [_paginating_](g) a list page.
@@ -2,4 +2,4 @@
 title: paginator
 ---

-A collection of [pagers](g).
+A _paginator_ is a collection of [_pagers_](g).
@@ -2,4 +2,4 @@
 title: parameter
 ---

-Typically, a user-defined key-value pair at the site or page level, but may also refer to a configuration setting or an [argument](g). See&nbsp;also&nbsp;[field](g).
+A _parameter_ is typically a user-defined key-value pair at the site or page level, but may also refer to a configuration setting or an [_argument_](g).
@@ -2,4 +2,4 @@
 title: partial
 ---

-A [template](g) called from any other template including [shortcodes](g), [render hooks](g), and other partials. A partial either renders something or returns something. A partial can also call itself, for example, to [walk](g) a data structure.
+A _partial_ is a [_template_](g) called from any other template including [_shortcodes_](g), [render hooks](g), and other partials. A partial either renders something or returns something. A partial can also call itself, for example, to [_walk_](g) a data structure.
@@ -2,4 +2,4 @@
 title: permalink
 ---

-The absolute URL of a published resource or a rendered page, including scheme and host.
+A _permalink_ is the absolute URL of a published resource or a rendered page, including scheme and host.
@@ -2,4 +2,4 @@
 title: pipe
 ---

-See [pipeline](g).
+See [_pipeline_](g).
@@ -2,6 +2,6 @@
 title: pipeline
 ---

-Within a [template action](g), a pipeline is a possibly chained sequence of values, [function](g) calls, or [method](g) calls. Functions and methods in the pipeline may take multiple [arguments](g).
+Within a [_template action_](g), a _pipeline_ is a possibly chained sequence of values, [_function_](g) calls, or [_method_](g) calls. Functions and methods in the pipeline may take multiple [_arguments_](g).

-A pipeline may be *chained* by separating a sequence of commands with pipeline characters "|". In a chained pipeline, the result of each command is passed as the last argument to the following command. The output of the final command in the pipeline is the value of the pipeline.
+A pipeline may be *chained* by separating a sequence of commands with pipeline characters (`|`). In a chained pipeline, the result of each command is passed as the last argument to the following command. The output of the final command in the pipeline is the value of the pipeline.
@@ -2,4 +2,4 @@
 title: publish
 ---

-See [build](g).
+See [_build_](g).
@@ -1,5 +1,6 @@
 ---
 title: raw string literal
+reference: https://go.dev/ref/spec#String_literals
 ---

 A _raw string literal_ is a character sequences between backticks, as in \`bar\`. Within the backticks, any character may appear except a backtick. Backslashes have no special meaning and the string may contain newlines. Carriage return characters (`\r`) inside raw string literals are discarded from the raw string value.
@@ -2,4 +2,4 @@
 title: regular page
 ---

-Content with the "page" [page kind](g). See also [section page](g).
+A _regular page_ is a page with the "page" [_page kind_](g). See also [_section page_](g).
@@ -2,4 +2,4 @@
 title: relative permalink
 ---

-The host-relative URL of a published resource or a rendered page.
+A _relative permalink_ is the host-relative URL of a published resource or a rendered page.
@@ -2,4 +2,4 @@
 title: remote resource
 ---

-A file on a remote server, accessible via HTTP or HTTPS with the [`resources.GetRemote`](/functions/resources/getremote) function.
+A _remote resource_ is a file on a remote server, accessible via HTTP or HTTPS.
@@ -3,4 +3,4 @@ title: render hook
 reference: /render-hooks
 ---

-A [template](g) that overrides standard Markdown rendering.
+A _render hook_ is a [_template_](g) that overrides standard Markdown rendering.
@@ -2,7 +2,7 @@
 title: resource type
 ---

-The main type of a resource's [media type]. Content files such as Markdown, HTML, AsciiDoc, Pandoc, reStructuredText, and Emacs Org Mode have resource type `page`. Other resource types include `image`, `video`, etc. Retrieve the resource type using the [`ResourceType`] method on a `Resource` object.
+A _resource type_ is the main type of a resource's [media type]. Content files such as Markdown, HTML, AsciiDoc, Pandoc, reStructuredText, and Emacs Org Mode have resource type `page`. Other resource types include `image`, `video`, etc. Retrieve the resource type using the [`ResourceType`] method on a `Resource` object.

 [media type]: /methods/resource/mediatype/
 [`ResourceType`]: /methods/resource/resourcetype/
@@ -2,6 +2,6 @@
 title: resource
 ---

-Any file consumed by the build process to augment or generate content, structure, behavior, or presentation. For example: images, videos, content snippets, CSS, Sass, JavaScript, and data.
+A _resource_ is any file consumed by the build process to augment or generate content, structure, behavior, or presentation. For example: images, videos, content snippets, CSS, Sass, JavaScript, and data.

-Hugo supports three types of resources: [global resources](g), [page resources](g), and [remote resources](g).
+Hugo supports three types of resources: [_global resources_](g), [_page resources_](g), and [_remote resources_](g).
@@ -2,4 +2,4 @@
 title: scalar
 ---

-A _scalar_ is a single value, one of [string](g), [integer](g), [floating point](g), or [boolean](g).
+A _scalar_ is a single value, one of [_string_](g), [_integer_](g), [floating point](g), or [_boolean_](g).
@@ -2,4 +2,4 @@
 title: scope
 ---

-The term _scope_ refers to the specific region of code where a [_variable_](g) or [_object_](g) is accessible. For example, a variable initialized in one template is not available within another.
+The term _scope_ refers to the specific region of code where a [_variable_](g) or [_object_](g) is accessible. For example, a variable initialized in one [template](g) is not available within another.
@@ -2,7 +2,7 @@
 title: scratch pad
 ---

-Conceptually, a [map](g) with [methods](g) to set, get, update, and delete values. Attach the data structure to a `Page` or `Site` object using the [`Store`] method, or create a locally scoped scratch pad using the [`newScratch`] function.
+Conceptually, a _scratch pad_ is a [_map_](g) with [_methods_](g) to set, get, update, and delete values. Attach the data structure to a `Page` or `Site` object using the [`Store`] method, or create a locally scoped scratch pad using the [`newScratch`] function.

 [`Store`]: /methods/page/store/
 [`newScratch`]: /functions/collections/newscratch/
@@ -2,4 +2,4 @@
 title: section page
 ---

-Content with the "section" [page kind](g). Typically a listing of [regular pages](g) and/or other section pages within the current [section](g).
+A _section page_ is a page with the "section" [_page kind_](g). Typically a listing of [_regular pages_](g) and/or other section pages within the current [_section_](g).
@@ -2,4 +2,4 @@
 title: segment
 ---

-A _segment_ is a subset of a site, filtered by [_logical path_](g), language, [_page kind_](g), and [_output format_](g).
+A _segment_ is a subset of a site, filtered by [_logical path_](g), language, [_page kind_](g), or [_output format_](g).
@@ -1,5 +1,6 @@
 ---
 title: slice
+reference: https://go.dev/ref/spec#Slice_types
 ---

-A numbered sequence of elements. Unlike Go's [array](g)  data type, slices are dynamically sized. [Elements](g)  within a slice can be [scalars](g), [arrays](g), [maps](g), pages, or other slices. See the [Go&nbsp;documentation](https://go.dev/ref/spec#Slice_types) for details.
+A _slice_ is a numbered sequence of elements. Unlike Go's [_array_](g) data type, slices are dynamically sized. [_Elements_](g) within a slice can be [_scalars_](g), [_arrays_](g), [_maps_](g), pages, or other slices.
@@ -2,4 +2,4 @@
 title: string
 ---

-A sequence of bytes. For example, `"What is 6 times 7?"`.
+A _string_ is a sequence of bytes. For example, `"What is 6 times 7?"`.
@@ -3,4 +3,4 @@ title: taxonomic weight
 reference: content-management/taxonomies/#order-taxonomies
 ---

-Defined in front matter and unique to each taxonomy, this [weight](g)  determines the sort order of page collections contained within a [`Taxonomy`](g)  object.
+Defined in front matter and unique to each taxonomy, a _taxonomic weight_ is a [_weight_](g) that determines the sort order of page collections contained within a [`Taxonomy`](g) object.
@@ -2,4 +2,4 @@
 title: taxonomy object
 ---

-A [map](g)  of [terms](g)  and the [weighted pages](g)  associated with each term.
+A _taxonomy object_ is a [_map_](g) of [_terms_](g) and the [weighted pages](g) associated with each term.
@@ -2,4 +2,4 @@
 title: taxonomy page
 ---

-Content with the "taxonomy" [page kind](g). Typically a listing of [terms](g) within a given [taxonomy](g).
+A _taxonomy page_ is a page with the "taxonomy" [_page kind_](g). Typically a listing of [_terms_](g) within a given [_taxonomy_](g).
@@ -2,5 +2,4 @@
 title: taxonomy
 reference: /content-management/taxonomies
 ---
-
-A group of related [terms](g)  used to classify content. For example, a "colors" taxonomy might include the terms "red", "green", and "blue".
+A _taxonomy_ is a group of related [_terms_](g) used to classify content. For example, a "colors" taxonomy might include the terms "red", "green", and "blue".
@@ -1,5 +1,6 @@
 ---
 title: template action
+reference: https://pkg.go.dev/text/template#hdr-Actions
 ---

-A data evaluation or control structure within a [template](g), delimited by "{{"&nbsp;and&nbsp;"}}". See the [Go&nbsp;documentation](https://pkg.go.dev/text/template#hdr-Actions) for details.
+A data evaluation or control structure within a [_template_](g), delimited by "{{"&nbsp;and&nbsp;"}}".
@@ -1,5 +1,6 @@
 ---
 title: template
+reference: /templates
 ---

-A file with [template actions](g), located within the `layouts` directory of a project, theme, or module. See&nbsp;[details](/templates/).
+A _template_ is a file with [_template actions_](g), located within the `layouts` directory of a project, theme, or module.
@@ -2,4 +2,4 @@
 title: term page
 ---

-Content with the "term" [page kind](g). Typically a listing of [regular pages](g) and [section pages](g) with a given [term](g).
+A _term page_ is a page with the "term" [_page kind_](g). Typically a listing of [_regular pages_](g) and [_section pages_](g) with a given [_term_](g).
@@ -1,5 +1,6 @@
 ---
 title: term
+reference: /content-management/taxonomies
 ---

-A member of a [taxonomy](g), used to classify content. See&nbsp;[details](/content-management/taxonomies/).
+A _term_ is a member of a [_taxonomy_](g), used to classify content.
@@ -2,4 +2,4 @@
 title: theme
 ---

-A packaged combination of [archetypes](g), assets, content, data, [templates](g), translation tables, static files, or configuration settings. A theme may serve as the basis for a new site, or to augment an existing site. See also [module](g).
+A _theme_ is a packaged combination of [_archetypes_](g), assets, content, data, [_templates_](g), translation tables, static files, or configuration settings. A theme may serve as the basis for a new site, or to augment an existing site.
@@ -2,4 +2,4 @@
 title: token
 ---

-An identifier within a format string, beginning with a colon and replaced with a value when rendered. For example, use tokens in format strings for both [permalinks](/content-management/urls/#permalinks) and [dates](/functions/time/format/#localization).
+A _token_ is an identifier within a format string, beginning with a colon and replaced with a value when rendered. For example, use tokens in format strings for both [permalinks](/content-management/urls/#permalinks) and [dates](/functions/time/format/#localization).
@@ -1,5 +1,6 @@
 ---
 title: unmarshal
+reference: /functions/transform/unmarshal/
 ---

-To transform a serialized object into a data structure. For example, transforming a JSON file into a [map](g) that you can access within a template. See [marshal](g).
+To _unmarshal_ is to transform a serialized object into a data structure. For example, transforming a JSON file into a [_map_](g) that you can access within a template.
@@ -2,4 +2,4 @@
 title: variable
 ---

-A user-defined [identifier](g) prepended with a `$` symbol, representing a value of any data type, initialized or assigned within a [template action](g). For example, `$foo`&nbsp;and&nbsp;`$bar` are variables.
+A _variable_ is a user-defined [_identifier_](g) prepended with a `$` symbol, representing a value of any data type, initialized or assigned within a [_template action_](g). For example, `$foo`&nbsp;and&nbsp;`$bar` are variables.
@@ -2,4 +2,4 @@
 title: walk
 ---

-To recursively traverse a nested data structure. For example, rendering a multilevel menu.
+To _walk_ is to recursively traverse a nested data structure. For example, rendering a multilevel menu.
@@ -2,4 +2,4 @@
 title: weight
 ---

-Used to position an element within a collection sorted by weight. Assign weights using non-zero integers. Lighter items float to the top, while heavier items sink to the bottom. Unweighted or zero-weighted elements are placed at the end of the collection. Weights are typically assigned to pages, menu entries, languages, and output formats.
+A _weight_ is a numeric value used to position an element within a sorted [collection](g). Assign weights using non-zero integers. Lighter items float to the top, while heavier items sink to the bottom. Unweighted or zero-weighted elements are placed at the end of the collection. Weights are typically assigned to pages, menu entries, languages, and output formats.
@@ -2,4 +2,4 @@
 title: weighted page
 ---

-Contained within a [`Taxonomy`](g) object, a weighted page is a [map](g) with two elements: a `Page` object, and its [taxonomic weight](g) as defined in front matter. Access the elements using the `Page` and `Weight` keys.
+Contained within a [_taxonomy object_](g), a _weighted page_ is a [_map_](g) with two [_elements_](g): a `Page` object, and its [_taxonomic weight_](g) as defined in front matter. Access the elements using the `Page` and `Weight` keys.