This commit also introduces a convention where these common JS config files, including `package.hugo.json`, gets mounted into:
```
assets/_jsconfig
´``
These files mapped to their real filename will be added to the environment when running PostCSS, Babel etc., so you can do `process.env.HUGO_FILE_TAILWIND_CONFIG_JS` to resolve the real filename.
But do note that `assets` is a composite/union filesystem, so if your config file is not meant to be overridden, name them something specific.
This commit also adds adds `workDir/node_modules` to `NODE_PATH` and `HUGO_WORKDIR` to the env when running the JS tools above.
Fixes#7644Fixes#7656Fixes#7675
Fill the .TableOfContents template variable when writing Asciidoc content.
This is done by letting Asciidoc render its TOC as HTML, then extract this
HTML rendered TOC, parse it into a tableofcontents.Root and finally remove
it from the HTML content.
This aims to stay in the logic that the Asciidoc parsing is entirely done
by the external helper.
See #1687
* Add instructions for using Macports
Fix for #688, rewrite the text so it's clear that either MacPorts or Homebrew can be used to install Hugo.
* Add MacPorts to Getting Started page
* Update Pick Your Method section to include MacPorts
It's contradicted two lines above :)
> You can also create type/section specific hooks in `layouts/[type/section]/_markup`, e.g.: `layouts/blog/_markup`.{{< new-in "0.71.0" >}}
Closes#1161
I removed the paragraph related to Amazon S3 deployment from Wercker;
I was unable to find any documentation on the Wercker site. This is not
surprising. Wercker was acquired by Oracle in 2017, and I suspect Oracle
has little interest in promoting any of Amazon's services.
This PR did hide the option to create an empty issue unexpectedly under a large link to the community. Not what I expected and sadly untestable. Sorry. I'll open another PR adding issue templates.
This config enables us to add external links to the process of creating new issues. I propose to add a friendly link to the community, just in case the issue opener is not aware of this forum.
