a7e1e9be8 Clarify front matter date fields 69df4fc22 Clarify how to determine if .Inner is populated 9046bf424 Document strings.ContainsNonSpace 8dbe5df90 Fix indentation and broken image 48ad4124e Typo: functions/after.md d4c01b57b Link to detailed descriptions of canonfiyURLs and relativeURLs 4d9597302 Explain behaviour when appending to a slice containing other slices 69e24e44e Standardize right arrow usage 01b378726 Remove references to Google's Universal Analytics and the async template d415bae24 Use shared file to describe regex syntax e75dee6b8 snap: How to enable or revoke access to SSH keys feed2d1c0 Remove hasPrefix and hasSuffix in favor of namespaced versions 3c6d2cfe5 security: Use default execution settings 461b5fcaf netlify: Hugo 0.116.1 95fac27a5 configuration: correct cacheDir description cd9f1f929 configuration: Fix broken link 605394de4 netlify: Upgrade to Hugo 0.116.0 baf2a0f7b Merge branch 'tempv0.116.0' ee51a9323 Update requirements for building from source 40189956d Editor tools: Remove duplicate sentence fb0ff2621 docs: Regenerate CLI docs e8a5665c4 Update where.md 7bc5cf15d Update hosting instructions 018a04314 docs: Update where d33ae91cf docs: Update where function operators 9a108a664 docs: Rework the cacheDir documentation git-subtree-dir: docs git-subtree-split: a7e1e9be851b95e636ab5360e5151156b4f89044
5.1 KiB
title | linkTitle | description | categories | keywords | menu | toc | weight | aliases | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Content summaries | Summaries | Hugo generates summaries of your content. |
|
|
|
true | 160 |
|
With the use of the .Summary
page variable, Hugo generates summaries of content to use as a short version in summary views.
Summary splitting options
- Automatic Summary Split
- Manual Summary Split
- Front Matter Summary
It is natural to accompany the summary with links to the original content, and a common design pattern is to see this link in the form of a "Read More ..." button. See the .RelPermalink
, .Permalink
, and .Truncated
page variables.
Automatic summary splitting
By default, Hugo automatically takes the first 70 words of your content as its summary and stores it into the .Summary
page variable for use in your templates. You may customize the summary length by setting summaryLength
in your site configuration.
{{% note %}}
You can customize how HTML tags in the summary are loaded using functions such as plainify
and safeHTML
.
{{% /note %}}
{{% note %}}
The Hugo-defined summaries are set to use word count calculated by splitting the text by one or more consecutive whitespace characters. If you are creating content in a CJK
language and want to use Hugo's automatic summary splitting, set hasCJKLanguage
to true
in your site configuration.
{{% /note %}}
Manual summary splitting
Alternatively, you may add the <!--more-->
summary divider where you want to split the article.
For Org mode content, use # more
where you want to split the article.
Content that comes before the summary divider will be used as that content's summary and stored in the .Summary
page variable with all HTML formatting intact.
{{% note %}} The concept of a summary divider is not unique to Hugo. It is also called the "more tag" or "excerpt separator" in other literature. {{% /note %}}
- 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) in each content file. This can be automated by adding the summary divider below the front matter of an archetype.
{{% warning "Be Precise with the Summary Divider" %}}
Be careful to enter <!--more-->
exactly; i.e., all lowercase and with no whitespace.
{{% /note %}}
Front matter summary
You might want your summary to be something other than the text that starts the article. In this case you can provide a separate summary in the summary
variable of the article front matter.
- Pros
- Complete freedom of text independent of the content of the article. Markup can be used within the summary.
- Cons
- Extra work for content authors as they need to write an entirely separate piece of text as the summary of the article.
Summary selection order
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:
- 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 - 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 - The text at the start of the article will be provided as per the automatic summary split method
{{% warning "Competing selections" %}}
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.
{{% /note %}}
Example: first 10 articles with summaries
You can show content summaries with the following code. You could use the following snippet, for example, in a section template.
{{< code file="page-list-with-summaries.html" >}} {{ range first 10 .Pages }}
{{ .Title }}
{{ .Summary }}Note how the .Truncated
boolean variable value may be used to hide the "Read More..." link when the content is not truncated; i.e., when the summary contains the entire article.