Current options are:
markup:
pandoc:
filters:
- list
- of
- filters
extensions:
- list
- of
- extensions
extraArgs:
- --extra-arguments
- --one-per-line
Generalize some Pandoc options.
Support configuring a bibliography in markup config
Anonymous Update
[pandoc] Allow page parameters to override site parameters.
This allows specifying things like this in the page frontmatter:
---
title: Something
bibliography:
source: mybibliography.bib
pandoc:
filter:
- make-diagrams.lua
...
These options are local to the page. Specifying the same under `markup`
in the site configuration applies those settings to all pages.
Paths (filters, bibliography, citation style) are resolved relative to
the page, site, and the `static` folder.
[pandoc] Support metadata
Support specifying Pandoc metadata in the site configuration and page
configuration using the following syntax:
Site (in `config.yaml`):
```yaml
markup:
pandoc:
metadata:
link-citations: true
```
Or in frontmatter:
```yaml
---
pandoc:
metadata:
link-citations: true
...
```
[pandoc] Simplify path management.
No need for any fancy path lookup gymnastics. `pandoc`'s
`--resource-path` option does the legwork of locating resources on
multiple directories.
[pandoc] Don't use x != "" to denote failure.
Current options are:
markup:
pandoc:
filters:
- list
- of
- filters
extensions:
- list
- of
- extensions
extraArgs:
- --extra-arguments
- --one-per-line
Generalize some Pandoc options.
Support configuring a bibliography in markup config
Anonymous Update
[pandoc] Allow page parameters to override site parameters.
This allows specifying things like this in the page frontmatter:
---
title: Something
bibliography:
source: mybibliography.bib
pandoc:
filter:
- make-diagrams.lua
...
These options are local to the page. Specifying the same under `markup`
in the site configuration applies those settings to all pages.
Paths (filters, bibliography, citation style) are resolved relative to
the page, site, and the `static` folder.
[pandoc] Support metadata
Support specifying Pandoc metadata in the site configuration and page
configuration using the following syntax:
Site (in `config.yaml`):
```yaml
markup:
pandoc:
metadata:
link-citations: true
```
Or in frontmatter:
```yaml
---
pandoc:
metadata:
link-citations: true
...
```
[pandoc] Simplify path management.
No need for any fancy path lookup gymnastics. `pandoc`'s
`--resource-path` option does the legwork of locating resources on
multiple directories.
[pandoc] Don't use x != "" to denote failure.
Primary motivation is documentation, but it will also hopefully simplify the code.
Also,
* Lower case the default output format names; this is in line with the custom ones (map keys) and how
it's treated all the places. This avoids doing `stringds.EqualFold` everywhere.
Closes#10896Closes#10620
This also speeds up situations where you only need the fragments/toc and not the rendered content, e.g. Related
with fragments type indexing:
```bash
name old time/op new time/op delta
RelatedSite-10 12.3ms ± 2% 10.7ms ± 1% -12.95% (p=0.029 n=4+4)
name old alloc/op new alloc/op delta
RelatedSite-10 38.6MB ± 0% 38.2MB ± 0% -1.08% (p=0.029 n=4+4)
name old allocs/op new allocs/op delta
RelatedSite-10 117k ± 0% 115k ± 0% -1.36% (p=0.029 n=4+4)
```
Fixes#10750
This ommmit contains some security hardening measures for the Hugo build runtime.
There are some rarely used features in Hugo that would be good to have disabled by default. One example would be the "external helpers".
For `asciidoctor` and some others we use Go's `os/exec` package to start a new process.
These are a predefined set of binary names, all loaded from `PATH` and with a predefined set of arguments. Still, if you don't use `asciidoctor` in your project, you might as well have it turned off.
You can configure your own in the new `security` configuration section, but the defaults are configured to create a minimal amount of site breakage. And if that do happen, you will get clear instructions in the loa about what to do.
The default configuration is listed below. Note that almost all of these options are regular expression _whitelists_ (a string or a slice); the value `none` will block all.
```toml
[security]
enableInlineShortcodes = false
[security.exec]
allow = ['^dart-sass-embedded$', '^go$', '^npx$', '^postcss$']
osEnv = ['(?i)^(PATH|PATHEXT|APPDATA|TMP|TEMP|TERM)$']
[security.funcs]
getenv = ['^HUGO_']
[security.http]
methods = ['(?i)GET|POST']
urls = ['.*']
```
This change is mostly motivated to get a more stable CI build (we're building the Hugo site there, with Instagram and Twitter shortcodes sometimes failing).
Fixes#7866
This commit also
* revises the change detection for templates used by content files in server mode.
* Adds a Page.RenderString method
Fixes#6545Fixes#4663Closes#6043
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:
```toml
[markup]
defaultMarkdownHandler="blackfriday"
```
Fixes#5963Fixes#1778Fixes#6355
This commmit prepares for the addition of Goldmark as the new Markdown renderer in Hugo.
This introduces a new `markup` package with some common interfaces and each implementation in its own package.
See #5963
