content: Add a "vendor" glossary entry

Author: jmooring

archetypes/glossary.md

@@ -1,13 +1,7 @@
 ---
-title: {{ replace .File.ContentBaseName "-" " " }}
-params:
-  reference: 
+title: vendor
 ---
 
-<!--
-Glossary terms are maintained on dedicated individual pages within the documentation. These pages act as a central repository for all term definitions, although they are not directly visible to site visitors.
+To _vendor_ (verb) in a software context is the process of including the source code of third-party dependencies directly within your own project's repository, rather than downloading them on the fly from an external package manager.
 
-Definitions must be presented in complete sentences, with the first sentence always explicitly introducing the term being defined. The first occurrence of the term itself, along with any other referenced glossary terms, should be presented in italics within the definition. However, when a term is an alias for another term, the definition can simply state "See [page kind]" (e.g., "See [page kind]"). These guidelines aim to enhance the readability and consistency of all glossary definitions.
-
-The "reference" field in the front matter of each definition page should be used to include a "See details" link at the end of the definition. This allows for flexible placement of the definition within the documentation while maintaining a central source for the definition itself. The value in the "reference" field must correspond to the logical path of the relevant page within the documentation structure.
--->
+  When you are asked to "vendor the dependencies into the project root," you are being told to move those external libraries from a temporary cache into a dedicated folder that gets committed to your version control system.

content/en/quick-reference/glossary/build.md

@@ -2,4 +2,4 @@
 title: build
 ---
 
-To _build_ a site is to generate HTML files and assets such as images, CSS files, and JavaScript files. The build process includes rendering and resource transformations.
+To _build_ (verb) a site is to generate HTML files and assets such as images, CSS files, and JavaScript files. The build process includes rendering and resource transformations.

content/en/quick-reference/glossary/chain.md

@@ -2,4 +2,4 @@
 title: chain
 ---
 
-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`.
+To _chain_ (verb) 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`.

content/en/quick-reference/glossary/marshal.md

@@ -3,4 +3,4 @@ title: marshal
 reference: /functions/transform/remarshal/
 ---
 
-To _marshal_ is to transform a data structure into a serialized object. For example, transforming a [_map_](g) into a JSON string.
+To _marshal_ (verb) is to transform a data structure into a serialized object. For example, transforming a [_map_](g) into a JSON string.

content/en/quick-reference/glossary/paginate.md

@@ -2,4 +2,4 @@
 title: paginate
 ---
 
-To _paginate_ is to split a list page into two or more subsets.
+To _paginate_ (verb) is to split a list page into two or more subsets.

content/en/quick-reference/glossary/unmarshal.md

@@ -3,4 +3,4 @@ title: unmarshal
 reference: /functions/transform/unmarshal/
 ---
 
-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.
+To _unmarshal_ (verb) 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.

content/en/quick-reference/glossary/vendor.md

@@ -0,0 +1,13 @@
+---
+title: {{ replace .File.ContentBaseName "-" " " }}
+params:
+  reference: 
+---
+
+<!--
+Glossary terms are maintained on dedicated individual pages within the documentation. These pages act as a central repository for all term definitions, although they are not directly visible to site visitors.
+
+Definitions must be presented in complete sentences, with the first sentence always explicitly introducing the term being defined. The first occurrence of the term itself, along with any other referenced glossary terms, should be presented in italics within the definition. However, when a term is an alias for another term, the definition can simply state "See [page kind]" (e.g., "See [page kind]"). These guidelines aim to enhance the readability and consistency of all glossary definitions.
+
+The "reference" field in the front matter of each definition page should be used to include a "See details" link at the end of the definition. This allows for flexible placement of the definition within the documentation while maintaining a central source for the definition itself. The value in the "reference" field must correspond to the logical path of the relevant page within the documentation structure.
+-->

content/en/quick-reference/glossary/walk.md

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