2021-September-4 Hugo v0.88.1 released. To keep up with Hugo releases, see discourse.gohugo.io/c/announcements, github.com/gohugoio/hugo/releases, gohugo.io/news, old.reddit.com/r/gohugo/, or twitter.com/@GoHugoIO.
2021-August-3 As of Hugo v0.87.0, which was released 2021-August-3, the Blackfriday built-in renderer is deprecated.
As of today, this evolving
has been on
2019-November-27 As of Hugo v0.60.0, which was released 2019-November-27, the Mmark built-in renderer is deprecated. There is a GitHub issue about upgrading Mmark rather than dropping it. In September 2021, this issue has 11 up votes.👍👍👍👍👍👍👍👍👍👍👍
Hugo versions 0.60.0 and newer 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 key-value pair in the file’s front matter
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.
Or the following in the TOML front matter of a content file.
markup = "identifier"
Possible markup identifiers are in the first column of the table above. In Hugo v0.74.0 through v0.88.1, you can put one of the following in the YAML front matter of a content file.
markup: ad markup: adoc markup: asciidoc markup: asciidocext # v0.74.0+ markup: blackfriday # v0.60.0+ markup: goldmark # v0.60.0+ markup: markdown markup: md markup: mdown markup: mmark # v0.88.1- markup: htm markup: html markup: org markup: pandoc markup: pdc markup: rst
It’s fine to use multiple markup languages in a single Hugo-generated project. For example, this Infinite Ink website includes content written in…
It’s possible to use multiple markup languages in a single Hugo-generated page. To learn about this see Infinite Ink’s A Way to Compare Hugo’s Markup Languages.
If you want Hugo to process a content file, it must have front matter. If you do not need to specify metadata, use empty front matter, for example this empty YAML front matter:
--- --- Begin writing markup here.
Or this empty TOML front matter:
+++ +++ Begin writing markup here.
markup: defaultMarkdownHandler: identifier
Or the following in your
[markup] defaultMarkdownHandler = "identifier"
identifier can by
In Hugo v0.59.1 and older…
the default Markdown renderer is Blackfriday,
is recognized in the front matter of a content file, but
are not available
as values of
is not recognized in a
config file (this
was introduced in v0.60.0).
“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:
For more about Hugo, see Infinite Ink’s…
.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 older use
goorgeous. Discussion about this in this issue.
.ad,Asciidoctor also recognizes
.txtas a file extension of an AsciiDoc file. 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 13 file extensions will be interpreted by
hugoas containing a known markup language:
Please comment so I know I'm not speaking into the void. Also, your public comment might improve this page or help me to improve this page.