Gopher
CONTENT MANAGEMENT

Content Summaries

Hugo generates summaries of your content.

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 .

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.

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 .

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:

  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
  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

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 .

page-list-with-summaries.html

{{ range first 10 .Pages }}
    <article>
      <!-- this <div> includes the title summary -->
      <div>
        <h2><a href="{{ .RelPermalink }}">{{ .Title }}</a></h2>
        {{ .Summary }}
      </div>
      {{ if .Truncated }}
      <!-- This <div> includes a read more link, but only if the summary is truncated... -->
      <div>
        <a href="{{ .RelPermalink }}">Read More…</a>
      </div>
      {{ end }}
    </article>
{{ end }}

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.