mirror/hugo
1
0
Fork 0
mirror of https://github.com/gohugoio/hugo.git synced 2025-08-29 22:29:56 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge commit 'a024bc7d76fcc5e49e8210f9b0896db9ef21861a'

Browse Source
This commit is contained in:
Bjørn Erik Pedersen
2025-02-13 10:40:34 +01:00
parent c054e18827 a024bc7d76
commit 304a7e5e74
817 changed files with 5301 additions and 14766 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/archetypes/glossary.md
View File

@@ -1,19 +1,12 @@
---
title: {{ replace .File.ContentBaseName "-" " " }}
reference:
---
<!--
You can insert these definitions in other pages using the `glossary-term` shortcode, so they must be self-contained.
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.
Do this:
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.
A _foo_ is big bar.
Not this:
A big bar.
Italicize the term whenever you use it in the definition.
An exception to this rule occurs when a term is an alias for another. In such cases, it is sufficient to use the phrase 'See [page kind]'."
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.
-->