Hugo versions 0.60.0 and later include support for the following markup languages.
To use one of
the last three markup languages,
need to install an external
Hugo determines the markup language of a content file that has one of the above 13 file extensions from…
markup parameter in the file’s front matter
or the file’s file extension.
The first of these found wins. This means that you can override the default meaning of a file extension by putting the following in the YAML front matter of a content file.
Possible identifiers are in the first column of the table above. For example, you could use one of the following.
markup: markdown markup: mmark markup: org markup: html markup: asciidoc markup: pandoc markup: rst markup: goldmark # v0.60.0+ markup: blackfriday # v0.60.0+
markup: defaultMarkdownHandler: blackfriday
In Hugo v0.59.1 and earlier…
To learn more about Hugo’s support for markup languages, see the following.
“ox-hugo is an Org exporter backend that exports Org to Hugo-compatible Markdown and also generates the front-matter (in TOML or YAML format).”
If you install…
you can create
R Markdown (
.Rmd) files that
blogdown — along with
hugo — will render
blogdown package installs and
For more about this, see:
Infinite Ink’s #gohugo Portal includes gohugo-related links from around the web, including:
.mkd. This way you and your text editor will interpret it as a Markdown file, but Hugo won’t. I do this with backup and other Markdown files that I do not want Hugo to process. For a discussion about this, see Avoid rendering of specific .md files from blogdown::serve_site() at stackoverflow.com.
go-org. Hugo versions 0.55.6 and earlier use
goorgeous. Discussion about this in this issue.
.ad,Asciidoctor also recognizes
.txtas file extensions of AsciiDoc files. This is useful if you want to hide the AsciiDocness of a content file, for example an include file, from Hugo.
content/directory, a file with one of the following file extensions will be interpreted by
hugoas containing a known markup language: