2022-May-31 Hugo v0.100.0 released and, as of this version, the Blackfriday built-in Markdown renderer is removed.
2022-January-12 Hugo v0.92.0 released and, as of this version, the Mmark built-in Markdown renderer is removed.
2021-October-22 Joe Mooring (@jmooring) posted GitHub Issue #9074: Mismatch between content format providers and file extensions. This issue is related to the file extensions discussed in this article.
As of today, this evolving
has been on
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 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 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 other words, you can put one of the following in the YAML front matter of a content file.
markup: ad markup: adoc markup: asciidoc # v0.73.0- (bug) markup: asciidocext # v0.74.0+ markup: blackfriday # v0.60.0 – v0.99.1 markup: goldmark # v0.60.0+ markup: markdown markup: md markup: mdown markup: mmark # v0.91.2- 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"
or another Markdown handler that
your version of
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.
.asciidocused to work but at some point (maybe v0.74.0) it quit working, which is probably a bug.
content/directory, a file with one of the following file extensions will be interpreted by
hugoas containing a known markup language:
Your public comment or question might immediately improve this page or help me to (eventually) improve this page.