<!--more--> summary divider where you want to split the article.
+Alternatively, you may add the `` summary divider where you want to split the article.
For [Org mode content][org], use `# more` where you want to split the article.
@@ -51,10 +53,10 @@ Pros
: Freedom, precision, and improved rendering. All HTML tags and formatting are preserved.
Cons
-: Extra work for content authors, since they need to remember to type <!--more--> (or `# more` for [org content][org]) in each content file. This can be automated by adding the summary divider below the front matter of an [archetype](/content-management/archetypes/).
+: Extra work for content authors, since they need to remember to type `` (or `# more` for [org content][org]) in each content file. This can be automated by adding the summary divider below the front matter of an [archetype](/content-management/archetypes/).
{{% note %}}
-Be careful to enter <!--more--> exactly; i.e., all lowercase and with no whitespace.
+Be careful to enter `` exactly; i.e., all lowercase and with no whitespace.
{{% /note %}}
### Front matter summary
@@ -71,12 +73,12 @@ Cons
Because there are multiple ways in which a summary can be specified it is useful to understand the order of selection Hugo follows when deciding on the text to be returned by `.Summary`. It is as follows:
-1. If there is a <!--more--> summary divider present in the article the text up to the divider will be provided as per the manual summary split method
+1. If there is a ``> summary divider present in the article the text up to the divider will be provided as per the manual summary split method
2. If there is a `summary` variable in the article front matter the value of the variable will be provided as per the front matter summary method
3. The text at the start of the article will be provided as per the automatic summary split method
{{% note %}}
-Hugo uses the _first_ of the above steps that returns text. So if, for example, your article has both `summary` variable in its front matter and a <!--more--> summary divider Hugo will use the manual summary split method.
+Hugo uses the _first_ of the above steps that returns text. So if, for example, your article has both `summary` variable in its front matter and a `` summary divider Hugo will use the manual summary split method.
{{% /note %}}
## Example: first 10 articles with summaries
diff --git a/content/en/functions/safe/CSS.md b/content/en/functions/safe/CSS.md
index de598835b..08307fb15 100644
--- a/content/en/functions/safe/CSS.md
+++ b/content/en/functions/safe/CSS.md
@@ -25,9 +25,9 @@ In this context, *safe* means CSS content that matches any of the following:
Example: Given `style = "color: red;"` defined in the front matter of your `.md` file:
-* `…
` → `…
` -* `…
` → `…
` +* `…
` → `…
` +* `…
` → `…
` {{% note %}} -"ZgotmplZ" is a special value that indicates that unsafe content reached a CSS or URL context. +`ZgotmplZ` is a special value that indicates that unsafe content reached a CSS or URL context. {{% /note %}} diff --git a/content/en/functions/safe/JS.md b/content/en/functions/safe/JS.md index 1e683e7af..65279b89b 100644 --- a/content/en/functions/safe/JS.md +++ b/content/en/functions/safe/JS.md @@ -22,5 +22,5 @@ Template authors are responsible for ensuring that typed expressions do not brea Example: Given `hash = "619c16f"` defined in the front matter of your `.md` file: -* `` → `` -* `` → `` +* `` → `` +* `` → `` diff --git a/content/en/functions/transform/Emojify.md b/content/en/functions/transform/Emojify.md index 81b0fdee0..d9f0adf67 100644 --- a/content/en/functions/transform/Emojify.md +++ b/content/en/functions/transform/Emojify.md @@ -15,7 +15,12 @@ aliases: [/functions/emojify] See the list of [emoji shortcodes] for available emoticons. -The `emojify` function can be called in your templates but not directly in your content files by default. For emojis in content files, set `enableEmoji` to `true` in your site's [configuration]. Then you can write emoji shorthand directly into your content files; e.g.I :heart: Hugo!:
+The `emojify` function can be called in your templates but not directly in your content files by default. For emojis in content files, set `enableEmoji` to `true` in your site's [configuration]. Then you can write emoji shorthand directly into your content files;
+
+
+```text
+I :heart: Hugo!
+```
I :heart: Hugo!
diff --git a/content/en/getting-started/glossary.md b/content/en/getting-started/glossary.md
index 90ac2e8c6..8a6af60d5 100644
--- a/content/en/getting-started/glossary.md
+++ b/content/en/getting-started/glossary.md
@@ -9,10 +9,9 @@ menu:
weight: 60
weight: 60
type: glossary
+# Use level 3 headings for each term in the glossary.
---
-
-
### action
See [template action](#template-action).
diff --git a/content/en/hugo-pipes/js.md b/content/en/hugo-pipes/js.md
index c742b2dad..f62458d39 100644
--- a/content/en/hugo-pipes/js.md
+++ b/content/en/hugo-pipes/js.md
@@ -90,7 +90,7 @@ defines
format
: (`string`) The output format.
One of: `iife`, `cjs`, `esm`.
- Default is `iife`, a self-executing function, suitable for inclusion as a