2021-May-02 Hugo v0.83.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.
2020-July-13 Hugo v0.74.0 released with “reworked external Asciidoctor integration.” To learn about this, see the v0.74.0 release notes, github.com/gohugoio/hugo/pull/7281, and gohugo.io/content-management/formats/. Thank you @muenchhausen (Derk Muenchhausen), @bwklein (Bryan Klein), @helfper (Helder Pereira), and all Hugo contributors!
As of today, this evolving
has been on the web for
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 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"
The 16 possible markup 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: asciidocext # v0.74.0+
It’s fine to use multiple markup languages in a single Hugo-generated website. For example, this Infinite Ink website includes content written in…
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 earlier…
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 earlier 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: