Merge commit 'cb39847dee488c373dd5bc2a3706385342a59355'

docs/content/en/content-management/image-processing/index.md

@@ -294,7 +294,7 @@ disableLatLong = false
 
 ## Smart Cropping of Images
 
-By default, Hugo will use the [Smartcrop](https://github.com/muesli/smartcrop), a library created by [muesli](https://github.com/muesli), when cropping images with `.Fill`. You can set the anchor point manually, but in most cases the smart option will make a good choice. And we will work with the library author to improve this in the future.
+By default, Hugo will use [Smartcrop](https://github.com/muesli/smartcrop), a library created by [muesli](https://github.com/muesli), when cropping images with `.Fill`. You can set the anchor point manually, but in most cases the smart option will make a good choice. And we will work with the library author to improve this in the future.
 
 An example using the sunset image from above:
 

docs/content/en/content-management/page-bundles.md

@@ -18,8 +18,8 @@ Page Bundles are a way to group [Page Resources](/content-management/page-resour
 
 A Page Bundle can be one of:
 
--   Leaf Bundle (leaf means it has no children)
--   Branch Bundle (home page, section, taxonomy terms, taxonomy list)
+- Leaf Bundle (leaf means it has no children)
+- Branch Bundle (home page, section, taxonomy terms, taxonomy list)
 
 |                                     | Leaf Bundle                                              | Branch Bundle                                                                                                                                                                                                      |
 |-------------------------------------|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------  |

docs/content/en/content-management/related.md

@@ -72,7 +72,7 @@ Hugo provides a sensible default configuration of Related Content, but you can f
 
 Without any `related` configuration set on the project, Hugo's Related Content methods will use the following.
 
-```yaml
+{{< code-toggle file="config" >}}
 related:
   threshold: 80
   includeNewer: false
@@ -82,7 +82,7 @@ related:
     weight: 100
   - name: date
     weight: 10
-```
+{{< /code-toggle >}}
 
 Custom configuration should be set using the same syntax.
 

docs/content/en/content-management/syntax-highlighting.md

@@ -16,14 +16,12 @@ aliases: [/extras/highlighting/,/extras/highlight/,/tools/syntax-highlighting/]
 toc: true
 ---
 
-
 Hugo uses [Chroma](https://github.com/alecthomas/chroma) as its code highlighter; it is built in Go and is really, really fast -- and for the most important parts compatible with Pygments we used before.
 
 ## Configure Syntax Highlighter
 
 See [Configure Highlight](/getting-started/configuration-markup#highlight).
 
-
 ## Generate Syntax Highlighter CSS
 
 If you run with `pygmentsUseClasses=true` in your site config, you need a style sheet.
@@ -36,7 +34,6 @@ hugo gen chromastyles --style=monokai > syntax.css
 
 Run `hugo gen chromastyles -h` for more options. See https://xyproto.github.io/splash/docs/ for a gallery of available styles.
 
-
 ## Highlight Shortcode
 
 Highlighting is carried out via the [built-in shortcode](/content-management/shortcodes/) `highlight`. `highlight` takes exactly one required parameter for the programming language to be highlighted and requires a closing shortcode. Note that `highlight` is *not* used for client-side javascript highlighting.
@@ -80,8 +77,6 @@ func GetTitleFunc(style string) func(s string) string {
 }
 {{< / highlight >}}
 
-
-
 ## Highlight Template Func
 
 See [Highlight](/functions/highlight/).

docs/content/en/contribute/themes.md

@@ -24,9 +24,8 @@ A collection of all themes created by the Hugo community, including screenshots
 
 Another great site for Hugo themes is [jamstackthemes.dev/](https://jamstackthemes.dev/ssg/hugo/).
 
-
 ### Add Your Theme to the Repo
 
-In order to add your Hugo theme to [themes.gohugo.io] please [open up a new issue in the theme repository](https://github.com/gohugoio/hugoThemes/issues/new?template=theme-submission.md). **Please make sure that you've read the theme submission guidelines in the [README](https://github.com/gohugoio/hugoThemes/blob/master/README.md#adding-a-theme-to-the-list) of the hugoThemes repository.** 
+In order to add your Hugo theme to [themes.gohugo.io] please [open up a new issue in the theme repository](https://github.com/gohugoio/hugoThemes/issues/new?template=theme-submission.md). **Please make sure that you've read the theme submission guidelines in the [README](https://github.com/gohugoio/hugoThemes/blob/master/README.md#adding-a-theme-to-the-list) of the hugoThemes repository.**
 
 [themes.gohugo.io]: https://themes.gohugo.io/

docs/content/en/functions/after.md

@@ -62,5 +62,5 @@ You can use `after` in combination with the [`first` function][] and Hugo's [pow
 
 [`first` function]: /functions/first/
 [list/section page]: /templates/section-templates/
-[lists]: /lists/
+[lists]: /templates/lists/#order-content
 [slice]: /functions/slice/

docs/content/en/hosting-and-deployment/deployment-with-wercker.md

@@ -289,8 +289,6 @@ Once this workflow is established, you can update your website automatically by
 
 [The source code for the site used in this guide is available on GitHub][guidesource], as is the [Wercker Hugo Build step][guidestep].
 
-If you want to see an example of how you can deploy to S3 instead of GitHub pages, check [Wercker's documentation][werckerdocs] for guidance on setup.
-
 [1]: /images/hosting-and-deployment/deployment-with-wercker/creating-a-basic-hugo-site.png
 [2]: /images/hosting-and-deployment/deployment-with-wercker/adding-the-project-to-github.png
 [3]: /images/hosting-and-deployment/deployment-with-wercker/wercker-sign-up.png
@@ -321,4 +319,3 @@ If you want to see an example of how you can deploy to S3 instead of GitHub page
 [hugoconfig]: /getting-started/configuration/
 [publicappurl]: https://app.wercker.com/#applications/5586dcbdaf7de9c51b02b0d5
 [quickstart]: /getting-started/quick-start/
-[werckerdocs]: http://devcenter.wercker.com/docs/deploy/s3.html

docs/content/en/hosting-and-deployment/hosting-on-bitbucket.md

@@ -56,11 +56,10 @@ In the rendered page response, the `https://__baseurl__` will be replaced with y
 
 We will now create a git repository and then push our code to Bitbucket. In Bitbucket, create a repository.
 
-![][1]
+![Bitbucket Screenshot][1]
 
 [1]: /images/hosting-and-deployment/hosting-on-bitbucket/bitbucket-create-repo.png
 
-
 ```
 # initialize new git repository
 git init
@@ -133,11 +132,10 @@ Your code will be committed to Bitbucket, Bitbucket Pipelines will run your buil
 
 At this point, you can now create and edit blog posts directly in the Bitbucket UI.
 
-![][2]
+![Bitbucket blog Screenshot][2]
 
 [2]: /images/hosting-and-deployment/hosting-on-bitbucket/bitbucket-blog-post.png
 
-
 ## Suggested next steps
 
 The code for this example can be found in this Bitbucket [repository](https://bitbucket.org/dundonian/hugo-docs-test). Aerobatic also provides a number of additional [plugins](https://www.aerobatic.com/docs) such as auth and redirects that you can use for your Hugo site.

docs/content/en/hosting-and-deployment/hosting-on-gitlab.md

@@ -77,6 +77,10 @@ That's it! You can now follow the CI agent building your page at `https://gitlab
 
 After the build has passed, your new website is available at `https://<YourUsername>.gitlab.io/<your-hugo-site>/`.
 
+{{% note %}}
+Make sure your `baseURL` key-value in your [site configuration](/getting-started/configuration/) reflects the full URL of your GitLab pages repository if you're using the default GitLab Pages URL (e.g., `https://<YourUsername>.gitlab.io/<your-hugo-site>/`) and not a custom domain.
+{{% /note %}}
+
 ## Next Steps
 
 GitLab supports using custom CNAME's and TLS certificates. For more details on GitLab Pages, see the [GitLab Pages setup documentation](https://about.gitlab.com/2016/04/07/gitlab-pages-setup/).

docs/content/en/hosting-and-deployment/hosting-on-keycdn.md

@@ -66,7 +66,7 @@ pages:
     - master
 
 ```
-Using this integration method,  you will have to specify the Zone ID and your [KeyCDN API](https://www.keycdn.com/api) key as secret variables. To do this, navigate to the top-left menu bar in GitLab and select Projects. Then, select your project and click on the Settings page. Finally, select Pipelines from the sub-menu and scroll down to the Secret Variable section. 
+Using this integration method,  you will have to specify the Zone ID and your [KeyCDN API](https://www.keycdn.com/api) key as secret variables. To do this, navigate to the top-left menu bar in GitLab and select Projects. Then, select your project and click on the Settings page. Finally, select Pipelines from the sub-menu and scroll down to the Secret Variable section.
 
 The Secret Variable for your Zone ID should look similar to:
 
@@ -89,6 +89,6 @@ git push -u origin master
 
 You can watch the progress and CI job output in your Gitlab project under “Pipelines”. 
 
-After verifying your CI job ran without issues, first check that your GitLab page shows up under `https://youruser.gitlab.io/reponame/` (it might look broken depending on your browser settings as all links point to your KeyCDN zone – don’t worry about that) and then by heading to whatever Zonealias / Zone URL you defined.
+After verifying your CI job ran without issues, first check that your GitLab page shows up under `https://youruser.gitlab.io/reponame/` (it might look broken depending on your browser settings as all links point to your KeyCDN zone – don’t worry about that) and then by heading to whatever Zone alias / Zone URL you defined.
 
 To learn more about Hugo hosting options with KeyCDN, check out the complete [Hugo hosting with KeyCDN integration guide](https://www.keycdn.com/support/hugo-hosting/).

docs/content/en/hugo-pipes/introduction.md

@@ -50,3 +50,15 @@ The example above can therefore also be written as follows:
 {{ $style := resources.Get "sass/main.scss" | toCSS | minify | fingerprint }}
 <link rel="stylesheet" href="{{ $style.Permalink }}">
 ```
+
+### Caching
+
+Hugo Pipes invocations are cached based on the entire _pipe chain_.
+
+An example of a pipe chain is:
+
+```go-html-template
+{{ $mainJs := resources.Get "js/main.js" | js.Build "main.js" | minify | fingerprint }}
+```
+
+The pipe chain is only invoked the first time it is encountered in a site build, and results are otherwise loaded from cache. As such, Hugo Pipes can be used in templates which are executed thousands or millions of times without negatively impacting the build performance.

docs/content/en/hugo-pipes/js.md

@@ -45,7 +45,7 @@ defines [map]
 {{ $defines := dict "process.env.NODE_ENV" `"development"` }}
 ```
 
-format [string] {{< new-in "0.75.0" >}}
+format [string] {{< new-in "0.74.3" >}}
 : The output format.
   One of: `iife`, `cjs`, `esm`.
   Default is `iife`, a self-executing function, suitable for inclusion as a <script> tag. 

docs/content/en/templates/internal.md

@@ -152,7 +152,7 @@ Various optional metadata can also be set:
 - The first 6 `tags` on the page are used for the tags metadata.
 - The `series` taxonomy is used to specify related "see also" pages by placing them in the same series.
 
-If using YouTube this will produce a og:video tag like `<meta property="og:video" content="url">`. If using a YouTube link make sure this is in **https://www.youtube.com/v/NlXVWtgLNjY** not __https://www.youtube.com/watch?v=NlXVWtgLNjY__
+If using YouTube this will produce a og:video tag like `<meta property="og:video" content="url">`. Use the `https://youtu.be/<id>` format with YouTube videos (example: `https://youtu.be/qtIqKaDlqXo`).
 
 ### Use the Open Graph Template
 

docs/content/en/variables/site.md

@@ -22,7 +22,7 @@ The following is a list of site-level (aka "global") variables. Many of these va
 
 ## Get the Site object from a partial
 
-All the methods below, e.g. `.Site.RegularPages` can also be reached via the global `site` function, e.g. `site.RegularPages`, which can be handy in partials where the `Page` object isn't easily available. {{< new-in "0.53.0" >}}.
+All the methods below, e.g. `.Site.RegularPages` can also be reached via the global `site` function, e.g. `site.RegularPages`, which can be handy in partials where the `Page` object isn't easily available. {{< new-in "0.53" >}}.
 
 ## Site Variables List
 

docs/netlify.toml

@@ -3,7 +3,7 @@ publish = "public"
 command = "hugo --gc --minify"
 
 [context.production.environment]
-HUGO_VERSION = "0.74.2"
+HUGO_VERSION = "0.74.3"
 HUGO_ENV = "production"
 HUGO_ENABLEGITINFO = "true"
 
@@ -11,20 +11,20 @@ HUGO_ENABLEGITINFO = "true"
 command = "hugo --gc --minify --enableGitInfo"
 
 [context.split1.environment]
-HUGO_VERSION = "0.74.2"
+HUGO_VERSION = "0.74.3"
 HUGO_ENV = "production"
 
 [context.deploy-preview]
 command = "hugo --gc --minify --buildFuture -b $DEPLOY_PRIME_URL"
 
 [context.deploy-preview.environment]
-HUGO_VERSION = "0.74.2"
+HUGO_VERSION = "0.74.3"
 
 [context.branch-deploy]
 command = "hugo --gc --minify -b $DEPLOY_PRIME_URL"
 
 [context.branch-deploy.environment]
-HUGO_VERSION = "0.74.2"
+HUGO_VERSION = "0.74.3"
 
 [context.next.environment]
 HUGO_ENABLEGITINFO = "true"