2c0125b52 Remove .Site.Author 2cf8841b3 Update partialCached.md (#1924) 385487191 Update data-templates.md (#1926) ce207e141 Remove redundant markdown and fix a few typos (#1936) 3687c2953 Make heading id linkable, take 2 45c79bea7 Make heading id linkable b22079344 Delete duplicates the lines 557-569 and 570-582. (#1934) 0a90dc122 Rework the taxonomy variables page (#1935) 7f8979c50 Update theme 26e682a3a Update multilingual.md d40e7693f Update postcss.md 375d75c01 Update postcss npm instructions (#1931) 63020094a Emphasize Window shell selection (#1930) 56824be2c Update configuration.md b7b8f16b3 Docu 'Theme components': minor fix (#1929) 09dc81a05 Remove Docker from BSD page (#1927) 205fea204 netlify: Hugo 0.108.0 6abe49c28 Merge commit 'da670c38ee63a7fef25e2b9f42519232055b60dc' 12b59a4c5 docs: Add basic doc for wrapStandAloneImageWithinParagraph etc. ba07bd970 dartsass: Add sourceMapIncludeSources option git-subtree-dir: docs git-subtree-split: 2c0125b5290494d49334606c451446ebd9df3c21
8.5 KiB
title | linktitle | description | date | publishdate | lastmod | categories | keywords | menu | weight | sections_weight | draft | aliases | toc | wip | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Internal Templates | Internal Templates | Hugo ships with a group of boilerplate templates that cover the most common use cases for static websites. | 2017-03-06 | 2017-03-06 | 2017-03-06 |
|
|
|
168 | 168 | false | true | true |
{{% warning %}} While the following internal templates are called similar to partials, they do not observe the partial template lookup order. {{% /warning %}}
Google Analytics
Hugo ships with internal templates supporting Google Analytics, both Google Analytics 4 (GA4) and Universal Analytics.
Note: Universal Analytics are deprecated. For details, see Universal Analytics will be going away.
Configure Google Analytics
Provide your tracking ID in your configuration file:
Google Analytics 4 (gtag.js) {{< code-toggle file="config" >}} googleAnalytics = "G-MEASUREMENT_ID" {{</ code-toggle >}}
Google Universal Analytics (analytics.js) {{< code-toggle file="config" >}} googleAnalytics = "UA-PROPERTY_ID" {{</ code-toggle >}}
Use the Google Analytics Template
You can then include the Google Analytics internal template:
{{ template "_internal/google_analytics_async.html" . }}
Note: The async template is not suitable for Google Analytics 4.
{{ template "_internal/google_analytics.html" . }}
If you want to create your own template, you can access the configured ID with {{ site.Config.Services.GoogleAnalytics.ID }}
.
Disqus
Hugo also ships with an internal template for Disqus comments, a popular commenting system for both static and dynamic websites. In order to effectively use Disqus, you will need to secure a Disqus "shortname" by signing up for the free service.
Configure Disqus
To use Hugo's Disqus template, you first need to set a single configuration value:
{{< code-toggle file="config" >}} disqusShortname = "your-disqus-shortname" {{</ code-toggle >}}
You also have the option to set the following in the front matter for a given piece of content:
disqus_identifier
disqus_title
disqus_url
Use the Disqus Template
To add Disqus, include the following line in templates where you want your comments to appear:
{{ template "_internal/disqus.html" . }}
A .Site.DisqusShortname
variable is also exposed from the config.
Conditional Loading of Disqus Comments
Users have noticed that enabling Disqus comments when running the Hugo web server on localhost
(i.e. via hugo server
) causes the creation of unwanted discussions on the associated Disqus account.
You can create the following layouts/partials/disqus.html
:
{{< code file="layouts/partials/disqus.html" download="disqus.html" >}}
comments powered by Disqus {{< /code >}}The if
statement skips the initialization of the Disqus comment injection when you are running on localhost
.
You can then render your custom Disqus partial template as follows:
{{ partial "disqus.html" . }}
Open Graph
An internal template for the Open Graph protocol, metadata that enables a page to become a rich object in a social graph. This format is used for Facebook and some other sites.
Configure Open Graph
Hugo's Open Graph template is configured using a mix of configuration variables and front-matter on individual pages.
{{< code-toggle file="config" >}} [params] title = "My cool site" images = ["site-feature-image.jpg"] description = "Text about my cool site" [taxonomies] series = "series" {{</ code-toggle >}}
{{< code-toggle file="content/blog/my-post" >}} title = "Post title" description = "Text about this post" date = "2006-01-02" images = ["post-cover.png"] audio = [] videos = [] series = [] tags = [] {{</ code-toggle >}}
Hugo uses the page title and description for the title and description metadata.
The first 6 URLs from the images
array are used for image metadata.
If page bundles are used and the images
array is empty or undefined, images with filenames matching *feature*
or *cover*,*thumbnail*
are used for image metadata.
Various optional metadata can also be set:
- Date, published date, and last modified data are used to set the published time metadata if specified.
audio
andvideos
are URL arrays likeimages
for the audio and video metadata tags, respectively.- The first 6
tags
on the page are used for the tags metadata. - The
series
taxonomy is used to specify related "see also" pages by placing them in the same series.
If using YouTube this will produce a og:video tag like <meta property="og:video" content="url">
. Use the https://youtu.be/<id>
format with YouTube videos (example: https://youtu.be/qtIqKaDlqXo
).
Use the Open Graph Template
To add Open Graph metadata, include the following line between the <head>
tags in your templates:
{{ template "_internal/opengraph.html" . }}
Twitter Cards
An internal template for Twitter Cards, metadata used to attach rich media to Tweets linking to your site.
Configure Twitter Cards
Hugo's Twitter Card template is configured using a mix of configuration variables and front-matter on individual pages.
{{< code-toggle file="config" >}} [params] images = ["site-feature-image.jpg"] description = "Text about my cool site" {{</ code-toggle >}}
{{< code-toggle file="content/blog/my-post" >}} title = "Post title" description = "Text about this post" images = ["post-cover.png"] {{</ code-toggle >}}
If images
aren't specified in the page front-matter, then hugo searches for image page resources with feature
, cover
, or thumbnail
in their name.
If no image resources with those names are found, the images defined in the site config are used instead.
If no images are found at all, then an image-less Twitter summary
card is used instead of summary_large_image
.
Hugo uses the page title and description for the card's title and description fields. The page summary is used if no description is given.
The .Site.Social.twitter
variable is exposed from the config as the value for twitter:site
.
{{< code-toggle file="config" >}} [social] twitter = "GoHugoIO" {{</ code-toggle >}}
NOTE: The @
will be added for you
<meta name="twitter:site" content="@GoHugoIO"/>
Use the Twitter Cards Template
To add Twitter card metadata, include the following line immediately after the <head>
element in your templates:
{{ template "_internal/twitter_cards.html" . }}
The Internal Templates
The code for these templates is located here.
_internal/disqus.html
_internal/google_analytics.html
_internal/google_analytics_async.html
_internal/opengraph.html
_internal/pagination.html
_internal/schema.html
_internal/twitter_cards.html