Hugo includes 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 # available in v0.60.0+ markup: blackfriday # available in v0.60.0+
In Hugo v0.60.0 and later the default Markdown renderer is Goldmark.
You can override this for your entire site by putting
the following in
markup: defaultMarkdownHandler: blackfriday
In v0.59.1 and earlier…
To learn more about Hugo’s support for markup languages, see gohugo.io’s…
“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:
go-org. Hugo v0.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 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: