--- 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 ``) 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 */%}} ``` ``` {{}} A bunch of code here {{}} ``` 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 `World`: ``` {{%/* 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: ``` {{}}

Hello World!

{{}} ``` ### 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 `
` 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" >}} {{}} {{< /code >}} #### Example `figure` Output {{< output file="figure-output-example.html" >}}

Steve Francia

{{< /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: ``` {{}} ``` #### 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" >}} {{}} {{< /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" >}} {{}}

{{ .Title }}

{{ range .Data.Pages }} {{ .Render "summary"}} {{ end }}
{{}} {{< /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" >}} <section id="main"> <div> <h1 id="title">{{ .Title }}</h1> {{ range .Data.Pages }} {{ .Render "summary"}} {{ end }} </div> </section> {{< /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" >}} {{}} {{< /code >}} You also have the option to hide the caption: {{< code file="instagram-input-hide-caption.md" >}} {{}} {{< /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]({{}}) [Who]({{}}) ``` #### Example `ref` and `relref` Output Assuming that standard Hugo pretty URLs are turned on. ``` Neat Who ``` ### `speakerdeck` To embed slides from [Speaker Deck][], click on "< /> Embed" (under Share right next to the template on Speaker Deck) and copy the URL: ``` ``` #### `speakerdeck` Example Input Extract the value from the field `data-id` and pass it to the shortcode: {{< code file="speakerdeck-example-input.md" >}} {{}} {{< /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" >}} {{}} {{< /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" >}} {{}} {{< /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 `
` that wraps the `