diff --git a/content/en/hugo-modules/use-modules.md b/content/en/hugo-modules/use-modules.md index 6af96c992..f29d4b198 100644 --- a/content/en/hugo-modules/use-modules.md +++ b/content/en/hugo-modules/use-modules.md @@ -148,7 +148,7 @@ use . use ../gohugoioTheme ``` -Using the `use` directive, list all the modules you want to work on, pointing to its relative location. As in the example above, it's recommended to always include the main project (the ".") in the list. +Using the `use` directive, list all the modules you want to work on, pointing to its relative location. As in the example above, it's recommended to always include the main project (the `.`) in the list. With that you can start the Hugo server with that workspace enabled: diff --git a/content/en/methods/page/Ancestors.md b/content/en/methods/page/Ancestors.md index da5cf2ca3..4fb00fc06 100644 --- a/content/en/methods/page/Ancestors.md +++ b/content/en/methods/page/Ancestors.md @@ -16,7 +16,7 @@ action: signatures: [PAGE.Ancestors] --- -{{% include "methods/page/_common/definition-of-section.md" %}} +{{% glossary-term section %}} With this content structure: diff --git a/content/en/methods/page/CurrentSection.md b/content/en/methods/page/CurrentSection.md index 17ec652c1..1684ee483 100644 --- a/content/en/methods/page/CurrentSection.md +++ b/content/en/methods/page/CurrentSection.md @@ -16,7 +16,7 @@ action: signatures: [PAGE.CurrentSection] --- -{{% include "methods/page/_common/definition-of-section.md" %}} +{{% glossary-term section %}} {{% note %}} The current section of a [section page](g), [taxonomy page](g), [term page](g), or the home page, is itself. diff --git a/content/en/methods/page/FirstSection.md b/content/en/methods/page/FirstSection.md index b3ae4c04a..29fbdc841 100644 --- a/content/en/methods/page/FirstSection.md +++ b/content/en/methods/page/FirstSection.md @@ -16,7 +16,7 @@ action: signatures: [PAGE.FirstSection] --- -{{% include "methods/page/_common/definition-of-section.md" %}} +{{% glossary-term section %}} {{% note %}} When called on the home page, the `FirstSection` method returns the `Page` object of the home page itself. diff --git a/content/en/methods/page/InSection.md b/content/en/methods/page/InSection.md index 75ceb2239..904f6ce75 100644 --- a/content/en/methods/page/InSection.md +++ b/content/en/methods/page/InSection.md @@ -19,7 +19,7 @@ toc: true 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. -{{% include "methods/page/_common/definition-of-section.md" %}} +{{% glossary-term section %}} With this content structure: diff --git a/content/en/methods/page/IsAncestor.md b/content/en/methods/page/IsAncestor.md index 17764fbe7..2613a2875 100644 --- a/content/en/methods/page/IsAncestor.md +++ b/content/en/methods/page/IsAncestor.md @@ -17,7 +17,7 @@ action: toc: true --- -{{% include "methods/page/_common/definition-of-section.md" %}} +{{% glossary-term section %}} With this content structure: diff --git a/content/en/methods/page/IsDescendant.md b/content/en/methods/page/IsDescendant.md index f2fc7e339..4ef7c6598 100644 --- a/content/en/methods/page/IsDescendant.md +++ b/content/en/methods/page/IsDescendant.md @@ -16,7 +16,7 @@ action: signatures: [PAGE1.IsDescendant PAGE2] --- -{{% include "methods/page/_common/definition-of-section.md" %}} +{{% glossary-term section %}} With this content structure: diff --git a/content/en/methods/page/Parent.md b/content/en/methods/page/Parent.md index db01eb589..4c182f8e1 100644 --- a/content/en/methods/page/Parent.md +++ b/content/en/methods/page/Parent.md @@ -16,7 +16,7 @@ action: signatures: [PAGE.Parent] --- -{{% include "methods/page/_common/definition-of-section.md" %}} +{{% glossary-term section %}} {{% note %}} The parent section of a regular page is the [current section]. diff --git a/content/en/methods/page/Sections.md b/content/en/methods/page/Sections.md index 4cce1a4fb..921e4eb4e 100644 --- a/content/en/methods/page/Sections.md +++ b/content/en/methods/page/Sections.md @@ -16,7 +16,7 @@ action: signatures: [PAGE.Sections] --- -{{% include "methods/page/_common/definition-of-section.md" %}} +{{% glossary-term section %}} With this content structure: diff --git a/content/en/methods/page/_common/definition-of-section.md b/content/en/methods/page/_common/definition-of-section.md deleted file mode 100644 index 4a2e36ff3..000000000 --- a/content/en/methods/page/_common/definition-of-section.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -_comment: Do not remove front matter. ---- - -A _section_ is a top-level content directory, or any content directory with an `_index.md` file. diff --git a/content/en/quick-reference/glossary/context.md b/content/en/quick-reference/glossary/context.md index ec39216c4..75afc709d 100644 --- a/content/en/quick-reference/glossary/context.md +++ b/content/en/quick-reference/glossary/context.md @@ -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. diff --git a/content/en/quick-reference/glossary/headless-bundle.md b/content/en/quick-reference/glossary/headless-bundle.md index 229d30894..ac7bf79c8 100644 --- a/content/en/quick-reference/glossary/headless-bundle.md +++ b/content/en/quick-reference/glossary/headless-bundle.md @@ -3,4 +3,4 @@ title: headless bundle reference: /content-management/build-options/ --- -A _headless bundle_ is an unpublished leaf or branch bundle whose content and resources you can include in other pages. +A _headless bundle_ is an unpublished [_leaf bundle_](g) or an unpublished [_branch bundle_](g) whose content and resources you can include in other pages. diff --git a/content/en/quick-reference/glossary/leaf-bundle.md b/content/en/quick-reference/glossary/leaf-bundle.md index a8eb03433..aa41384ee 100644 --- a/content/en/quick-reference/glossary/leaf-bundle.md +++ b/content/en/quick-reference/glossary/leaf-bundle.md @@ -3,4 +3,4 @@ title: leaf bundle reference: /content-management/page-bundles/ --- -A _leaf bundle_ is a directory that contains an `index.md` 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. +A _leaf bundle_ is a directory that contains an `index.md` file and zero or more [_resources_](g). Analogous to a physical leaf, a leaf bundle is at the end of a [_branch bundle_](g). It has no descendants. diff --git a/content/en/quick-reference/glossary/section.md b/content/en/quick-reference/glossary/section.md index 4ab7c976e..45d1203e0 100644 --- a/content/en/quick-reference/glossary/section.md +++ b/content/en/quick-reference/glossary/section.md @@ -2,4 +2,4 @@ title: section --- -A _section_ is a top-level content directory or any content directory containing an `_index.md` file. A section is also known as a [_branch bundle_](g). +A _section_ is a top-level content directory or any content directory containing an `_index.md` file.