Merge commit 'aa54803a84208816e9c678359bd3f86760484ce0'

docs/content/en/content-management/front-matter.md

@@ -160,12 +160,14 @@ show_comments: false
 Any node or section can pass down to descendents a set of Front Matter values as long as defined underneath the reserved `cascade` Front Matter key.
 
 ### Example
-```yaml
+
-# content/blog/_index.md
+In `content/blog/_index.md`
+
+{{< code-toggle copy="false" >}}
 title: Blog
 cascade:
   banner: images/typewriter.jpg
-```
+{{</ code-toggle >}}
 
 With the above example the Blog section page and its descendents will return `images/typewriter.jpg` when `.Params.banner` is invoked unless:
 

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

@@ -333,7 +333,7 @@ Using the preceding `tweet` example, the following simulates the displayed exper
 
 ### `vimeo`
 
-Adding a video from [Vimeo][] is equivalent to the YouTube shortcode above.
+Adding a video from [Vimeo][] is equivalent to the [YouTube Input shortcode][].
 
 ```
 https://vimeo.com/channels/staffpicks/146022717
@@ -431,3 +431,4 @@ To learn more about creating custom shortcodes, see the [shortcode template docu
 [templatessection]: /templates/
 [Vimeo]: https://vimeo.com/
 [YouTube Videos]: https://www.youtube.com/
+[YouTube Input shortcode]: #youtube

docs/content/en/getting-started/installing.md

@@ -305,9 +305,6 @@ Make the directory containing the source your working directory and then fetch H
 mkdir -p src/github.com/gohugoio
 ln -sf $(pwd) src/github.com/gohugoio/hugo
 
-# set the build path for Go
-export GOPATH=$(pwd)
-
 go get
 ```
 

docs/content/en/hosting-and-deployment/hugo-deploy.md

@@ -54,7 +54,7 @@ In the configuration file for your site, add a `[deployment]` section with one
 or more `[[deployment.targets]]` section, one for each deployment target. Here's
 a detailed example:
 
-```
+```toml
 [deployment]
 # By default, files are uploaded in an arbitrary order.
 # Files that match the regular expressions in the "Order" list
@@ -116,7 +116,8 @@ gzip = true
 ## Deploy
 
 To deploy to a target:
-```
+
+```bash
 hugo deploy [--target=<target name>, defaults to first target]
 ```
 

docs/content/en/news/0.67.0-relnotes/index.md

@@ -1,14 +1,14 @@
 
 ---
 date: 2020-03-09
-title: "0.67.0"
+title: "Hugo 0.67.0: Custom HTTP headers"
-description: "0.67.0"
+description: "This version brings Custom HTTP headers to the development server and exclude/include filters in Hugo Deploy."
 categories: ["Releases"]
 ---
 
-	The two main items in Hugo 0.67.0 is custom HTTP header support in `hugo server` and incldue/exclude filters for [Hugo Deploy](https://gohugo.io/hosting-and-deployment/hugo-deploy/#readout).
+The two main items in Hugo 0.67.0 is custom HTTP header support in `hugo server` and include/exclude filters for [Hugo Deploy](https://gohugo.io/hosting-and-deployment/hugo-deploy/#readout).
 
-Being able to [configure HTTP headers]https://gohugo.io/getting-started/configuration/#configure-server) in your development server means that you can now verify how your site behaves with the intended Content Security Policy settings etc., e.g.:
+Being able to [configure HTTP headers](https://gohugo.io/getting-started/configuration/#configure-server) in your development server means that you can now verify how your site behaves with the intended Content Security Policy settings etc., e.g.:
 
 ```toml
 [server]

docs/content/en/news/0.67.1-relnotes/index.md

@@ -2,7 +2,7 @@
 ---
 date: 2020-03-15
 title: "Hugo 0.67.1: A couple of Bug Fixes"
-description: "This version fixes a couple of bugs introduced in 0.67.0."
+description: "This version comes with some useful bug fixes."
 categories: ["Releases"]
 images:
 - images/blog/hugo-bug-poster.png
@@ -11,7 +11,7 @@ images:
 
 	
 
-This is a bug-fix release with a couple of important fixes.
+Some minor fixes:
 
 * metrics: Fix --templateMetricsHints [5eadc4c0](https://github.com/gohugoio/hugo/commit/5eadc4c0a8e5c51e72670591c4b7877e79c15e3c) [@bep](https://github.com/bep) [#7048](https://github.com/gohugoio/hugo/issues/7048)
 * resources: Add data context to the key in ExecuteAsTemplate [18cb21ff](https://github.com/gohugoio/hugo/commit/18cb21ff2e4a60e7094908e4d6113a9d5a086316) [@bep](https://github.com/bep) [#7046](https://github.com/gohugoio/hugo/issues/7046)

docs/content/en/tools/search.md

@@ -31,3 +31,4 @@ A static website with a dynamic search function? Yes, Hugo provides an alternati
 
 * [Algolia](https://www.algolia.com/)'s Search API makes it easy to deliver a great search experience in your apps and websites. Algolia Search provides hosted full-text, numerical, faceted, and geolocalized search.
 * [Bonsai](https://www.bonsai.io) is a fully-managed hosted Elasticsearch service that is fast, reliable, and simple to set up. Easily ingest your docs from Hugo into Elasticsearch following [this guide from the docs](https://docs.bonsai.io/docs/hugo).
+* [ExpertRec](https://www.expertrec.com/) is a hosted search-as-a-service solution that is fast and scalable. Set-up and integration is extremely easy and takes only a few minutes. The search settings can be modified without coding using a dashboard.

docs/netlify.toml

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