Skip to content
Browse files

Add Goldmark as the new default markdown handler

This commit adds the fast and CommonMark compliant Goldmark as the new default markdown handler in Hugo.

If you want to continue using BlackFriday as the default for md/markdown extensions, you can use this configuration:


Fixes #5963
Fixes #1778
Fixes #6355
  • Loading branch information
bep committed Nov 6, 2019
1 parent a3fe5e5 commit bfb9613a14ab2d93a4474e5486d22e52a9d5e2b3
Showing with 3,421 additions and 1,665 deletions.
  1. +1 −1 commands/genchromastyles.go
  2. +0 −12 docs/config.toml
  3. +5 −11 docs/config/_default/config.toml
  4. +1 −1 docs/content/en/about/
  5. +22 −176 docs/content/en/content-management/
  6. +66 −115 docs/content/en/content-management/
  7. +1 −0 docs/content/en/contribute/
  8. +2 −4 docs/content/en/functions/
  9. +73 −0 docs/content/en/getting-started/
  10. +5 −43 docs/content/en/getting-started/
  11. +0 −6 docs/content/en/getting-started/
  12. +0 −197 docs/content/en/readfiles/
  13. +0 −4 docs/content/en/templates/
  14. +161 −6 docs/data/docs.json
  15. +34 −0 docs/layouts/shortcodes/code-toggle.html
  16. +8 −0 docs/layouts/shortcodes/new-in.html
  17. +0 −1 docs/requirements.txt
  18. +2 −1 go.mod
  19. +4 −4 go.sum
  20. +15 −30 helpers/content.go
  21. +0 −27 helpers/general.go
  22. +11 −2 helpers/general_test.go
  23. +0 −402 helpers/pygments.go
  24. +0 −300 helpers/pygments_test.go
  25. +0 −1 hugolib/case_insensitive_test.go
  26. +0 −5 hugolib/config.go
  27. +19 −10 hugolib/hugo_sites_build_test.go
  28. +10 −4 hugolib/page__meta.go
  29. +13 −5 hugolib/page__per_output.go
  30. +144 −24 hugolib/page_test.go
  31. +12 −0 hugolib/shortcode_test.go
  32. +1 −1 hugolib/site_benchmark_new_test.go
  33. +11 −11 hugolib/site_test.go
  34. +2 −2 hugolib/testhelpers_test.go
  35. +3 −4 markup/asciidoc/convert.go
  36. +70 −0 markup/blackfriday/blackfriday_config/config.go
  37. +11 −32 markup/blackfriday/convert.go
  38. +9 −22 markup/blackfriday/convert_test.go
  39. +2 −3 markup/blackfriday/renderer.go
  40. +30 −7 markup/converter/converter.go
  41. +233 −0 markup/goldmark/convert.go
  42. +219 −0 markup/goldmark/convert_test.go
  43. +74 −0 markup/goldmark/goldmark_config/config.go
  44. +102 −0 markup/goldmark/toc.go
  45. +76 −0 markup/goldmark/toc_test.go
  46. +188 −0 markup/highlight/config.go
  47. +59 −0 markup/highlight/config_test.go
  48. +132 −0 markup/highlight/highlight.go
  49. +87 −0 markup/highlight/highlight_test.go
  50. +512 −0 markup/highlight/temphighlighting/highlighting.go
  51. +335 −0 markup/highlight/temphighlighting/highlighting_test.go
  52. +0 −108 markup/internal/blackfriday.go
  53. +56 −8 markup/markup.go
  54. +105 −0 markup/markup_config/config.go
  55. +69 −0 markup/markup_config/config_test.go
  56. +16 −6 markup/markup_test.go
  57. +12 −20 markup/mmark/convert.go
  58. +4 −9 markup/mmark/convert_test.go
  59. +6 −8 markup/mmark/renderer.go
  60. +3 −4 markup/org/convert.go
  61. +3 −4 markup/pandoc/convert.go
  62. +3 −5 markup/rst/convert.go
  63. +148 −0 markup/tableofcontents/tableofcontents.go
  64. +119 −0 markup/tableofcontents/tableofcontents_test.go
  65. +51 −0 parser/lowercase_camel_json.go
  66. +42 −16 tpl/transform/remarshal.go
  67. +17 −1 tpl/transform/remarshal_test.go
  68. +1 −1 tpl/transform/transform.go
  69. +1 −1 tpl/transform/transform_test.go
@@ -68,7 +68,7 @@ func (g *genChromaStyles) generate() error {
if err != nil {
return err
formatter := html.New(html.WithClasses())
formatter := html.New(html.WithClasses(true))
formatter.WriteCSS(os.Stdout, style)
return nil
@@ -15,18 +15,6 @@ pluralizeListTitles = false
# We do redirects via Netlify's _redirects file, generated by Hugo (see "outputs" below).
disableAliases = true

# Highlighting config (Pygments)
# It is (currently) not in use, but you can do ```go in a content file if you want to.
pygmentsCodeFences = true

pygmentsOptions = ""
# Use the Chroma stylesheet
pygmentsUseClasses = true
pygmentsUseClassic = false

# See
pygmentsStyle = "trac"

min = "0.56.0"
@@ -14,17 +14,11 @@ pluralizeListTitles = false
# We do redirects via Netlify's _redirects file, generated by Hugo (see "outputs" below).
disableAliases = true

# Highlighting config (Pygments)
# It is (currently) not in use, but you can do ```go in a content file if you want to.
pygmentsCodeFences = true

pygmentsOptions = ""
# Use the Chroma stylesheet
pygmentsUseClasses = true
pygmentsUseClassic = false

# See
pygmentsStyle = "trac"
style = "trac"
lineNumbersInTable = true
noClasses = false

home = [ "HTML", "RSS", "REDIR", "HEADERS" ]
@@ -52,7 +52,7 @@ toc: true
* Integrated [Google Analytics][] support
* Automatic [RSS][] creation
* Support for [Go][], [Amber], and [Ace][] HTML templates
* [Syntax highlighting][] powered by [Chroma][] (partly compatible with Pygments)
* [Syntax highlighting][] powered by [Chroma][]

[Ace]: /templates/alternatives/
@@ -1,6 +1,6 @@
title: Supported Content Formats
linktitle: Supported Content Formats
title: Content Formats
linktitle: Content Formats
description: Both HTML and Markdown are supported content formats.
date: 2017-01-10
publishdate: 2017-01-10
@@ -13,191 +13,37 @@ menu:
weight: 20
weight: 20 #rem
draft: false
aliases: [/content/markdown-extras/,/content/supported-formats/,/doc/supported-formats/,/tutorials/mathjax/]
aliases: [/content/markdown-extras/,/content/supported-formats/,/doc/supported-formats/]
toc: true

**Markdown is the main content format** and comes in two flavours: The excellent [Blackfriday project][blackfriday] (name your files `*.md` or set `markup = "markdown"` in front matter) or its fork [Mmark][mmark] (name your files `*.mmark` or set `markup = "mmark"` in front matter), both very fast markdown engines written in Go.
You can put any file type into your `/content` directories, but Hugo uses the `markup` front matter value if set or the file extension (see `Markup identifiers` in the table below) to determine if the markup needs to be processed, e.g.:

For Emacs users, [go-org]( provides built-in native support for Org-mode (name your files `*.org` or set `markup = "org"` in front matter)
* Markdown converted to HTML
* [Shortcodes](/content-management/shortcodes/) processed
* Layout applied

But in many situations, plain HTML is what you want. Just name your files with `.html` or `.htm` extension inside your content folder. Note that if you want your HTML files to have a layout, they need front matter. It can be empty, but it has to be there:
## List of content formats

title: "This is a content file in HTML"

<h1>Hello, Hugo!</h1>

{{% note "Deeply Nested Lists" %}}
Before you begin writing your content in markdown, Blackfriday has a known issue [(#329)]( with handling deeply nested lists. Luckily, there is an easy workaround. Use 4-spaces (i.e., <kbd>tab</kbd>) rather than 2-space indentations.
{{% /note %}}

## Configure BlackFriday Markdown Rendering

You can configure multiple aspects of Blackfriday as shown in the following list. See the docs on [Configuration][config] for the full list of explicit directions you can give to Hugo when rendering your site.

{{< readfile file="/content/en/readfiles/" markdown="true" >}}

## Extend Markdown

Hugo provides some convenient methods for extending markdown.

### Task Lists

Hugo supports [GitHub-styled task lists (i.e., TODO lists)][gfmtasks] for the Blackfriday markdown renderer. If you do not want to use this feature, you can disable it in your configuration.

#### Example Task List Input

{{< code file="content/" >}}
- [ ] a task list item
- [ ] list syntax required
- [ ] incomplete
- [x] completed
{{< /code >}}

#### Example Task List Output

The preceding markdown produces the following HTML in your rendered website:

<ul class="task-list">
<li><input type="checkbox" disabled="" class="task-list-item"> a task list item</li>
<li><input type="checkbox" disabled="" class="task-list-item"> list syntax required</li>
<li><input type="checkbox" disabled="" class="task-list-item"> incomplete</li>
<li><input type="checkbox" checked="" disabled="" class="task-list-item"> completed</li>

#### Example Task List Display

The following shows how the example task list will look to the end users of your website. Note that visual styling of lists is up to you. This list has been styled according to [the Hugo Docs stylesheet][hugocss].

- [ ] a task list item
- [ ] list syntax required
- [ ] incomplete
- [x] completed

### Emojis

To add emojis directly to content, set `enableEmoji` to `true` in your [site configuration][config]. To use emojis in templates or shortcodes, see [`emojify` function][].

For a full list of emojis, see the [Emoji cheat sheet][emojis].

### Shortcodes

If you write in Markdown and find yourself frequently embedding your content with raw HTML, Hugo provides built-in shortcodes functionality. This is one of the most powerful features in Hugo and allows you to create your own Markdown extensions very quickly.

See [Shortcodes][sc] for usage, particularly for the built-in shortcodes that ship with Hugo, and [Shortcode Templating][sct] to learn how to build your own.

### Code Blocks

Hugo supports GitHub-flavored markdown's use of triple back ticks, as well as provides a special [`highlight` shortcode][hlsc], and syntax highlights those code blocks natively using *Chroma*. Users also have an option to use *Pygments* instead. See the [Syntax Highlighting][hl] section for details.

## Mmark

Mmark is a [fork of BlackFriday][mmark] and markdown superset that is well suited for writing [IETF documentation][ietf]. You can see examples of the syntax in the [Mmark GitHub repository][mmark] or the full syntax on [Miek Gieben's website][].

### Use Mmark

As Hugo ships with Mmark, using the syntax is as easy as changing the extension of your content files from `.md` to `.mmark`.

In the event that you want to only use Mmark in specific files, you can also define the Mmark syntax in your content's front matter:

title: My Post
date: 2017-04-01
markup: mmark

{{% warning %}}
Thare are some features not available in Mmark; one example being that shortcodes are not translated when used in an included `.mmark` file ([#3131](, and `EXTENSION_ABBREVIATION` ([#1970]( and the aforementioned GFM todo lists ([#2270]( are not fully supported. Contributions are welcome.
{{% /warning %}}

## MathJax with Hugo

[MathJax]( is a JavaScript library that allows the display of mathematical expressions described via a LaTeX-style syntax in the HTML (or Markdown) source of a web page. As it is a pure a JavaScript library, getting it to work within Hugo is fairly straightforward, but does have some oddities that will be discussed here.

This is not an introduction into actually using MathJax to render typeset mathematics on your website. Instead, this page is a collection of tips and hints for one way to get MathJax working on a website built with Hugo.

### Enable MathJax

The first step is to enable MathJax on pages that you would like to have typeset math. There are multiple ways to do this (adventurous readers can consult the [Loading and Configuring]( section of the MathJax documentation for additional methods of including MathJax), but the easiest way is to use the secure MathJax CDN by include a `<script>` tag for the officially recommended secure CDN ([](

{{< code file="add-mathjax-to-page.html" >}}
<script type="text/javascript" src="">
{{< /code >}}

One way to ensure that this code is included in all pages is to put it in one of the templates that live in the `layouts/partials/` directory. For example, I have included this in the bottom of my template `footer.html` because I know that the footer will be included in every page of my website.

### Options and Features

MathJax is a stable open-source library with many features. I encourage the interested reader to view the [MathJax Documentation](, specifically the sections on [Basic Usage]( and [MathJax Configuration Options](

### Issues with Markdown

{{% note %}}
The following issues with Markdown assume you are using `.md` for content and BlackFriday for parsing. Using [Mmark](#mmark) as your content format will obviate the need for the following workarounds.

When using Mmark with MathJax, use `displayMath: [['$$','$$'], ['\\[','\\]']]`. See the [Mmark ``]( for more information. In addition to MathJax, Mmark has been shown to work well with [KaTeX]( See this [related blog post from a Hugo user](
{{% /note %}}

After enabling MathJax, any math entered between proper markers (see the [MathJax documentation][mathjaxdocs]) will be processed and typeset in the web page. One issue that comes up, however, with Markdown is that the underscore character (`_`) is interpreted by Markdown as a way to wrap text in `emph` blocks while LaTeX (MathJax) interprets the underscore as a way to create a subscript. This "double speak" of the underscore can result in some unexpected and unwanted behavior.

### Solution

There are multiple ways to remedy this problem. One solution is to simply escape each underscore in your math code by entering `\_` instead of `_`. This can become quite tedious if the equations you are entering are full of subscripts.

Another option is to tell Markdown to treat the MathJax code as verbatim code and not process it. One way to do this is to wrap the math expression inside a `<div>` `</div>` block. Markdown would ignore these sections and they would get passed directly on to MathJax and processed correctly. This works great for display style mathematics, but for inline math expressions the line break induced by the `<div>` is not acceptable. The syntax for instructing Markdown to treat inline text as verbatim is by wrapping it in backticks (`` ` ``). You might have noticed, however, that the text included in between backticks is rendered differently than standard text (on this site these are items highlighted in red). To get around this problem, we could create a new CSS entry that would apply standard styling to all inline verbatim text that includes MathJax code. Below I will show the HTML and CSS source that would accomplish this (note this solution was adapted from [this blog post]( credit goes to the original author).

{{< code file="mathjax-markdown-solution.html" >}}
<script type="text/x-mathjax-config">
tex2jax: {
inlineMath: [['$','$'], ['\\(','\\)']],
displayMath: [['$$','$$'], ['\[','\]']],
processEscapes: true,
processEnvironments: true,
skipTags: ['script', 'noscript', 'style', 'textarea', 'pre'],
TeX: { equationNumbers: { autoNumber: "AMS" },
extensions: ["AMSmath.js", "AMSsymbols.js"] }
{{< /code >}}

As before, this content should be included in the HTML source of each page that will be using MathJax. The next code snippet contains the CSS that is used to have verbatim MathJax blocks render with the same font style as the body of the page.

{{< code file="mathjax-style.css" >}}
code.has-jax {
font: inherit;
font-size: 100%;
background: inherit;
border: inherit;
color: #515151;
{{< /code >}}

In the CSS snippet, notice the line `color: #515151;`. `#515151` is the value assigned to the `color` attribute of the `body` class in my CSS. In order for the equations to fit in with the body of a web page, this value should be the same as the color of the body.

### Usage
The current list of content formats in Hugo:

With this setup, everything is in place for a natural usage of MathJax on pages generated using Hugo. In order to include inline mathematics, just put LaTeX code in between `` `$ TeX Code $` `` or `` `\( TeX Code \)` ``. To include display style mathematics, just put LaTeX code in between `<div>$$TeX Code$$</div>`. All the math will be properly typeset and displayed within your Hugo generated web page!
| Name | Markup identifiers | Comment |
| ------------- | ------------- |-------------|
| Goldmark | md, markdown, goldmark |Note that you can set the default handler of `md` and `markdown` to something else, see [Configure Markup](/getting-started/configuration-markup/).{{< new-in "0.60.0" >}} |
| Blackfriday | blackfriday |Blackfriday will eventually be deprecated.|
|MMark|mmark|Mmark is deprecated and will be removed in a future release.|
|Emacs Org-Mode|org|See [go-org](|
|Asciidoc|asciidoc, adoc, ad|Needs Asciidoc or [Asciidoctor][ascii] installed.|
|RST|rst|Needs [RST]( installed.|
|Pandoc|pandoc, pdc|Needs [Pandoc]( installed.|
|HTML|html, htm|To be treated as a content file, with layout, shortcodes etc., it must have front matter. If not, it will be copied as-is.|

## Additional Formats Through External Helpers
The `markup identifier` is fetched from either the `markup` variable in front matter or from the file extension. For markup-related configuration, see [Configure Markup](/getting-started/configuration-markup/).

Hugo has a new concept called _external helpers_. It means that you can write your content using [Asciidoc][ascii], [reStructuredText][rest], or [pandoc]. If you have files with associated extensions, Hugo will call external commands to generate the content. ([See the Hugo source code for external helpers][helperssource].)

For example, for Asciidoc files, Hugo will try to call the `asciidoctor` or `asciidoc` command. This means that you will have to install the associated tool on your machine to be able to use these formats. ([See the Asciidoctor docs for installation instructions](
## External Helpers

To use these formats, just use the standard extension and the front matter exactly as you would do with natively supported `.md` files.
Some of the formats in the table above needs external helpers installed on your PC. For example, for Asciidoc files, Hugo will try to call the `asciidoctor` or `asciidoc` command. This means that you will have to install the associated tool on your machine to be able to use these formats. ([See the Asciidoctor docs for installation instructions](

Hugo passes reasonable default arguments to these external helpers by default:

0 comments on commit bfb9613

Please sign in to comment.
You can’t perform that action at this time.