mirror of
https://github.com/gohugoio/hugo.git
synced 2024-11-21 20:46:30 -05:00
50ec65fbe1
ef02e34e Correct the mmark example frontmatter parameter 6e91e900 SectionPagesMenu > sectionPagesMenu 1a0db1a6 Adjust sectionPagesMenu f9f87d9d Fix extension's missing period. 7062ae07 Remove Press and Articles page 771f2b38 Remove outdated and redudant content file for release notes 64cf47c3 Remove outdated note in docs contribution guide bdb11b89 Fix typo 8324af70 Fixes broken link on Roadmap d93f0992 functions: Add all missing binary comparison operators fb7ae80a Fix typo in usage.md fbdae08b Fix typo in content-management/taxonomies.md 66fab8d2 Make <title> less stuttery b3cd4c22 Remove old temp release notes 5589ba96 Fix typos in templates/lists.md af3a0807 http > HTTP b2af90ae Remove formatting in description of blog article 6e2e60a9 Add blog article about Netlify files 0bb6f2f2 Use title in archetype file 7b2490ff Get the Archetypes up to new spec f401d69b Load CSS and JS via HTTP/2 server push 4aef4944 Adjust titles 362acdb2 Fix typo in quickstart c2440560 Remove inline icons from installation guide d2edcbc3 Revert "Fix links to Disqus template documentation" 622f49cf Add a full commands section at the quick start end 752f065b Fix server command in README 93e08e19 Fix links to Disqus template documentation 5e0cfaa9 Adjust Linux install d51397c2 Fix broken link in Quick Start 1fb39846 Add /quickstart alias to quickstart 7440616b Add new and simpler quickstart b3ec6986 Let page title correspond to function name replaceRE b44499c9 Add YouTube tutorial about taxonomies 88b9eb0e Add RSS templates example 6c0bde3f Update slice.md 6c212ea6 Reorder to match the following content order d2122992 Complete "content" spelling under theme components e4824eb3 Fix the output shortcode and its usage 0adfc945 Add archetypes YouTube video 638e9d9b Fix double "your" typo in taxonomies.md git-subtree-dir: docs git-subtree-split: ef02e34eaf296c3f94b4446b3c3347771e786057
395 lines
14 KiB
Markdown
395 lines
14 KiB
Markdown
---
|
|
title: Shortcodes
|
|
linktitle:
|
|
description: Shortcodes are simple snippets inside your content files calling built-in or custom templates.
|
|
godocref:
|
|
date: 2017-02-01
|
|
publishdate: 2017-02-01
|
|
lastmod: 2017-03-31
|
|
menu:
|
|
docs:
|
|
parent: "content-management"
|
|
weight: 35
|
|
weight: 35 #rem
|
|
categories: [content management]
|
|
#tags: [markdown,content,shortcodes]
|
|
draft: false
|
|
aliases: [/extras/shortcodes/]
|
|
toc: true
|
|
---
|
|
|
|
## What a Shortcode is
|
|
|
|
Hugo loves Markdown because of its simple content format, but there are times when Markdown falls short. Often, content authors are forced to add raw HTML (e.g., video `<iframes>`) to Markdown content. We think this contradicts the beautiful simplicity of Markdown's syntax.
|
|
|
|
Hugo created **shortcodes** to circumvent these limitations.
|
|
|
|
A shortcode is a simple snippet inside a content file that Hugo will render using a predefined template. Note that shortcodes will not work in template files. If you need the type of drop-in functionality that shortcodes provide but in a template, you most likely want a [partial template][partials] instead.
|
|
|
|
In addition to cleaner Markdown, shortcodes can be updated any time to reflect new classes, techniques, or standards. At the point of site generation, Hugo shortcodes will easily merge in your changes. You avoid a possibly complicated search and replace operation.
|
|
|
|
## Use Shortcodes
|
|
|
|
In your content files, a shortcode can be called by calling `{{%/* shortcodename parameters */%}}`. Shortcode parameters are space delimited, and parameters with internal spaces can be quoted.
|
|
|
|
The first word in the shortcode declaration is always the name of the shortcode. Parameters follow the name. Depending upon how the shortcode is defined, the parameters may be named, positional, or both, although you can't mix parameter types in a single call. The format for named parameters models that of HTML with the format `name="value"`.
|
|
|
|
Some shortcodes use or require closing shortcodes. Again like HTML, the opening and closing shortcodes match (name only) with the closing declaration, which is prepended with a slash.
|
|
|
|
Here are two examples of paired shortcodes:
|
|
|
|
```
|
|
{{%/* mdshortcode */%}}Stuff to `process` in the *center*.{{%/* /mdshortcode */%}}
|
|
```
|
|
|
|
```
|
|
{{</* highlight go */>}} A bunch of code here {{</* /highlight */>}}
|
|
```
|
|
|
|
The examples above use two different delimiters, the difference being the `%` character in the first and the `<>` characters in the second.
|
|
|
|
### Shortcodes with Markdown
|
|
|
|
The `%` character indicates that the shortcode's inner content---called in the [shortcode template][sctemps] with the [`.Inner` variable][scvars]---needs further processing by the page's rendering processor (i.e. markdown via Blackfriday). In the following example, Blackfriday would convert `**World**` to `<strong>World</strong>`:
|
|
|
|
```
|
|
{{%/* myshortcode */%}}Hello **World!**{{%/* /myshortcode */%}}
|
|
```
|
|
|
|
### Shortcodes Without Markdown
|
|
|
|
The `<` character indicates that the shortcode's inner content does *not* need further rendering. Often shortcodes without markdown include internal HTML:
|
|
|
|
```
|
|
{{</* myshortcode */>}}<p>Hello <strong>World!</strong></p>{{</* /myshortcode */>}}
|
|
```
|
|
|
|
### Nested Shortcodes
|
|
|
|
You can call shortcodes within other shortcodes by creating your own templates that leverage the `.Parent` variable. `.Parent` allows you to check the context in which the shortcode is being called. See [Shortcode templates][sctemps].
|
|
|
|
## Use Hugo's Built-in Shortcodes
|
|
|
|
Hugo ships with a set of predefined shortcodes that represent very common usage. These shortcodes are provided for author convenience and to keep your markdown content clean.
|
|
|
|
### `figure`
|
|
|
|
`figure` is an extension of the image syntax in markdown, which does not provide a shorthand for the more semantic [HTML5 `<figure>` element][figureelement].
|
|
|
|
The `figure` shortcode can use the following named parameters:
|
|
|
|
* `src`
|
|
* `link`
|
|
* `title`
|
|
* `caption`
|
|
* `class`
|
|
* `attr` (i.e., attribution)
|
|
* `attrlink`
|
|
* `alt`
|
|
|
|
#### Example `figure` Input
|
|
|
|
{{< code file="figure-input-example.md" >}}
|
|
{{</* figure src="/media/spf13.jpg" title="Steve Francia" */>}}
|
|
{{< /code >}}
|
|
|
|
#### Example `figure` Output
|
|
|
|
{{< output file="figure-output-example.html" >}}
|
|
<figure>
|
|
<img src="/media/spf13.jpg" />
|
|
<figcaption>
|
|
<h4>Steve Francia</h4>
|
|
</figcaption>
|
|
</figure>
|
|
{{< /output >}}
|
|
|
|
### `gist`
|
|
|
|
Bloggers often want to include GitHub gists when writing posts. Let's suppose we want to use the [gist at the following url][examplegist]:
|
|
|
|
```
|
|
https://gist.github.com/spf13/7896402
|
|
```
|
|
|
|
We can embed the gist in our content via username and gist ID pulled from the URL:
|
|
|
|
```
|
|
{{</* gist spf13 7896402 */>}}
|
|
```
|
|
|
|
#### Example `gist` Input
|
|
|
|
If the gist contains several files and you want to quote just one of them, you can pass the filename (quoted) as an optional third argument:
|
|
|
|
{{< code file="gist-input.md" >}}
|
|
{{</* gist spf13 7896402 "img.html" */>}}
|
|
{{< /code >}}
|
|
|
|
#### Example `gist` Output
|
|
|
|
{{< output file="gist-output.html" >}}
|
|
{{< gist spf13 7896402 >}}
|
|
{{< /output >}}
|
|
|
|
#### Example `gist` Display
|
|
|
|
To demonstrate the remarkably efficiency of Hugo's shortcode feature, we have embedded the `spf13` `gist` example in this page. The following simulates the experience for visitors to your website. Naturally, the final display will be contingent on your stylesheets and surrounding markup.
|
|
|
|
{{< gist spf13 7896402 >}}
|
|
|
|
### `highlight`
|
|
|
|
This shortcode will convert the source code provided into syntax-highlighted HTML. Read more on [highlighting](/tools/syntax-highlighting/). `highlight` takes exactly one required `language` parameter and requires a closing shortcode.
|
|
|
|
#### Example `highlight` Input
|
|
|
|
{{< code file="content/tutorials/learn-html.md" >}}
|
|
{{</* highlight html */>}}
|
|
<section id="main">
|
|
<div>
|
|
<h1 id="title">{{ .Title }}</h1>
|
|
{{ range .Data.Pages }}
|
|
{{ .Render "summary"}}
|
|
{{ end }}
|
|
</div>
|
|
</section>
|
|
{{</* /highlight */>}}
|
|
{{< /code >}}
|
|
|
|
#### Example `highlight` Output
|
|
|
|
The `highlight` shortcode example above would produce the following HTML when the site is rendered:
|
|
|
|
{{< output file="tutorials/learn-html/index.html" >}}
|
|
<span style="color: #f92672"><section</span> <span style="color: #a6e22e">id=</span><span style="color: #e6db74">"main"</span><span style="color: #f92672">></span>
|
|
<span style="color: #f92672"><div></span>
|
|
<span style="color: #f92672"><h1</span> <span style="color: #a6e22e">id=</span><span style="color: #e6db74">"title"</span><span style="color: #f92672">></span>{{ .Title }}<span style="color: #f92672"></h1></span>
|
|
{{ range .Data.Pages }}
|
|
{{ .Render "summary"}}
|
|
{{ end }}
|
|
<span style="color: #f92672"></div></span>
|
|
<span style="color: #f92672"></section></span>
|
|
{{< /output >}}
|
|
|
|
{{% note "More on Syntax Highlighting" %}}
|
|
To see even more options for adding syntax-highlighted code blocks to your website, see [Syntax Highlighting in Developer Tools](/tools/syntax-highlighting/).
|
|
{{% /note %}}
|
|
|
|
### `instagram`
|
|
|
|
If you'd like to embed a photo from [Instagram][], you only need the photo's ID. You can discern an Instagram photo ID from the URL:
|
|
|
|
```
|
|
https://www.instagram.com/p/BWNjjyYFxVx/
|
|
```
|
|
|
|
#### Example `instagram` Input
|
|
|
|
{{< code file="instagram-input.md" >}}
|
|
{{</* instagram BWNjjyYFxVx */>}}
|
|
{{< /code >}}
|
|
|
|
You also have the option to hide the caption:
|
|
|
|
{{< code file="instagram-input-hide-caption.md" >}}
|
|
{{</* instagram BWNjjyYFxVx hidecaption */>}}
|
|
{{< /code >}}
|
|
|
|
#### Example `instagram` Output
|
|
|
|
By adding the preceding `hidecaption` example, the following HTML will be added to your rendered website's markup:
|
|
|
|
{{< output file="instagram-hide-caption-output.html" >}}
|
|
{{< instagram BWNjjyYFxVx hidecaption >}}
|
|
{{< /output >}}
|
|
|
|
#### Example `instagram` Display
|
|
|
|
Using the preceding `instagram` with hidecaption` example above, the following simulates the displayed experience for visitors to your website. Naturally, the final display will be contingent on your stylesheets and surrounding markup.
|
|
|
|
{{< instagram BWNjjyYFxVx hidecaption >}}
|
|
|
|
|
|
### `ref` and `relref`
|
|
|
|
These shortcodes will look up the pages by their relative path (e.g., `blog/post.md`) or their logical name (`post.md`) and return the permalink (`ref`) or relative permalink (`relref`) for the found page.
|
|
|
|
`ref` and `relref` also make it possible to make fragmentary links that work for the header links generated by Hugo.
|
|
|
|
{{% note "More on Cross References" %}}
|
|
Read a more extensive description of `ref` and `relref` in the [cross references](/content-management/cross-references/) documentation.
|
|
{{% /note %}}
|
|
|
|
`ref` and `relref` take exactly one required parameter of _reference_, quoted and in position `0`.
|
|
|
|
#### Example `ref` and `relref` Input
|
|
|
|
```
|
|
[Neat]({{</* ref "blog/neat.md" */>}})
|
|
[Who]({{</* relref "about.md#who" */>}})
|
|
```
|
|
|
|
#### Example `ref` and `relref` Output
|
|
|
|
Assuming that standard Hugo pretty URLs are turned on.
|
|
|
|
```
|
|
<a href="/blog/neat">Neat</a>
|
|
<a href="/about/#who:c28654c202e73453784cfd2c5ab356c0">Who</a>
|
|
```
|
|
|
|
### `speakerdeck`
|
|
|
|
To embed slides from [Speaker Deck][], click on "< /> Embed" (under Share right next to the template on Speaker Deck) and copy the URL:
|
|
|
|
```
|
|
<script async class="speakerdeck-embed" data-id="4e8126e72d853c0060001f97" data-ratio="1.33333333333333" src="//speakerdeck.com/assets/embed.js"></script>
|
|
```
|
|
|
|
#### `speakerdeck` Example Input
|
|
|
|
Extract the value from the field `data-id` and pass it to the shortcode:
|
|
|
|
{{< code file="speakerdeck-example-input.md" >}}
|
|
{{</* speakerdeck 4e8126e72d853c0060001f97 */>}}
|
|
{{< /code >}}
|
|
|
|
#### `speakerdeck` Example Output
|
|
|
|
{{< output file="speakerdeck-example-input.md" >}}
|
|
{{< speakerdeck 4e8126e72d853c0060001f97 >}}
|
|
{{< /output >}}
|
|
|
|
#### `speakerdeck` Example Display
|
|
|
|
For the preceding `speakerdeck` example, the following simulates the displayed experience for visitors to your website. Naturally, the final display will be contingent on your stylesheets and surrounding markup.
|
|
|
|
{{< speakerdeck 4e8126e72d853c0060001f97 >}}
|
|
|
|
### `tweet`
|
|
|
|
You want to include a single tweet into your blog post? Everything you need is the URL of the tweet:
|
|
|
|
```
|
|
https://twitter.com/spf13/status/877500564405444608
|
|
```
|
|
|
|
#### Example `tweet` Input
|
|
|
|
Pass the tweet's ID from the URL as a parameter to the `tweet` shortcode:
|
|
|
|
{{< code file="example-tweet-input.md" >}}
|
|
{{</* tweet 877500564405444608 */>}}
|
|
{{< /code >}}
|
|
|
|
#### Example `tweet` Output
|
|
|
|
Using the preceding `tweet` example, the following HTML will be added to your rendered website's markup:
|
|
|
|
{{< output file="example-tweet-output.html" >}}
|
|
{{< tweet 877500564405444608 >}}
|
|
{{< /output >}}
|
|
|
|
#### Example `tweet` Display
|
|
|
|
Using the preceding `tweet` example, the following simulates the displayed experience for visitors to your website. Naturally, the final display will be contingent on your stylesheets and surrounding markup.
|
|
|
|
{{< tweet 877500564405444608 >}}
|
|
|
|
### `vimeo`
|
|
|
|
Adding a video from [Vimeo][] is equivalent to the YouTube shortcode above.
|
|
|
|
```
|
|
https://vimeo.com/channels/staffpicks/146022717
|
|
```
|
|
|
|
#### Example `vimeo` Input
|
|
|
|
Extract the ID from the video's URL and pass it to the `vimeo` shortcode:
|
|
|
|
{{< code file="example-vimeo-input.md" >}}
|
|
{{</* vimeo 146022717 */>}}
|
|
{{< /code >}}
|
|
|
|
#### Example `vimeo` Output
|
|
|
|
Using the preceding `vimeo` example, the following HTML will be added to your rendered website's markup:
|
|
|
|
{{< output file="example-vimeo-output.html" >}}
|
|
{{< vimeo 146022717 >}}
|
|
{{< /output >}}
|
|
|
|
{{% tip %}}
|
|
If you want to further customize the visual styling of the YouTube or Vimeo output, add a `class` named parameter when calling the shortcode. The new `class` will be added to the `<div>` that wraps the `<iframe>` *and* will remove the inline styles. Note that you will need to call the `id` as a named parameter as well.
|
|
|
|
```
|
|
{{</* vimeo id="146022717" class="my-vimeo-wrapper-class" */>}}
|
|
```
|
|
{{% /tip %}}
|
|
|
|
#### Example `vimeo` Display
|
|
|
|
Using the preceding `vimeo` example, the following simulates the displayed experience for visitors to your website. Naturally, the final display will be contingent on your stylesheets and surrounding markup.
|
|
|
|
{{< vimeo 146022717 >}}
|
|
|
|
### `youtube`
|
|
|
|
The `youtube` shortcode embeds a responsive video player for [YouTube videos][]. Only the ID of the video is required, e.g.:
|
|
|
|
```
|
|
https://www.youtube.com/watch?v=w7Ft2ymGmfc
|
|
```
|
|
|
|
|
|
#### Example `youtube` Input
|
|
|
|
Copy the YouTube video ID that follows `v=` in the video's URL and pass it to the `youtube` shortcode:
|
|
|
|
{{< code file="example-youtube-input.md" >}}
|
|
{{</* youtube w7Ft2ymGmfc */>}}
|
|
{{< /code >}}
|
|
|
|
Furthermore, you can automatically start playback of the embedded video by setting the `autoplay` parameter to `true`. Remember that you can't mix named an unnamed parameters, so you'll need to assign the yet unnamed video id to the parameter `id`:
|
|
|
|
|
|
{{< code file="example-youtube-input-with-autoplay.md" >}}
|
|
{{</* youtube id="w7Ft2ymGmfc" autoplay="true" */>}}
|
|
{{< /code >}}
|
|
|
|
#### Example `youtube` Output
|
|
|
|
Using the preceding `youtube` example, the following HTML will be added to your rendered website's markup:
|
|
|
|
{{< code file="example-youtube-output.html" >}}
|
|
{{< youtube id="w7Ft2ymGmfc" autoplay="true" >}}
|
|
{{< /code >}}
|
|
|
|
#### Example `youtube` Display
|
|
|
|
Using the preceding `youtube` example (without `autoplay="true"`), the following simulates the displayed experience for visitors to your website. Naturally, the final display will be contingent on your stylesheets and surrounding markup. The video is also include in the [Quick Start of the Hugo documentation][quickstart].
|
|
|
|
{{< youtube w7Ft2ymGmfc >}}
|
|
|
|
## Create Custom Shortcodes
|
|
|
|
To learn more about creating custom shortcodes, see the [shortcode template documentation][].
|
|
|
|
[`figure` shortcode]: #figure
|
|
[contentmanagementsection]: /content-management/formats/
|
|
[examplegist]: https://gist.github.com/spf13/7896402
|
|
[figureelement]: http://html5doctor.com/the-figure-figcaption-elements/ "An article from HTML5 doctor discussing the fig and figcaption elements."
|
|
[Instagram]: https://www.instagram.com/
|
|
[pagevariables]: /variables/page/
|
|
[partials]: /templates/partials/
|
|
[Pygments]: http://pygments.org/
|
|
[quickstart]: /getting-started/quick-start/
|
|
[sctemps]: /templates/shortcode-templates/
|
|
[scvars]: /variables/shortcodes/
|
|
[shortcode template documentation]: /templates/shortcode-templates/
|
|
[Speaker Deck]: https://speakerdeck.com/
|
|
[templatessection]: /templates/
|
|
[Vimeo]: https://vimeo.com/
|
|
[YouTube Videos]: https://www.youtube.com/
|