Release Hugo 0.45

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

@@ -17,10 +17,10 @@ menu:
 
 ## The Image Page Resource
 
-The `image` is a [Page Resource]({{< relref "content-management/page-resources" >}}), and the processing methods listed below does not work on images inside your `/static` folder.
+The `image` is a [Page Resource]({{< relref "/content-management/page-resources" >}}), and the processing methods listed below does not work on images inside your `/static` folder.
 
 
-To get all images in a [Page Bundle]({{< relref "content-management/organization#page-bundles" >}}):
+To get all images in a [Page Bundle]({{< relref "/content-management/organization#page-bundles" >}}):
 
 
 ```go-html-template

content/en/content-management/multilingual.md

@@ -231,7 +231,7 @@ By setting the `translationKey` front matter param to `about` in all three pages
 
 Because paths and filenames are used to handle linking, all translated pages, except for the language part, will be sharing the same url.
 
-To localize the URLs, the [`slug`]({{< ref "content-management/organization/index.md#slug" >}}) or [`url`]({{< ref "content-management/organization/index.md#url" >}}) front matter param can be set in any of the non-default language file. 
+To localize the URLs, the [`slug`]({{< ref "/content-management/organization/index.md#slug" >}}) or [`url`]({{< ref "/content-management/organization/index.md#url" >}}) front matter param can be set in any of the non-default language file. 
 
 For example, a french translation (`content/about.fr.md`) can have its own localized slug.
 

content/en/content-management/organization/index.md

@@ -21,7 +21,7 @@ toc: true
 
 Hugo `0.32` announced page-relative images and other resources packaged into `Page Bundles`. 
 
-These terms are connected, and you also need to read about [Page Resources]({{< relref "content-management/page-resources" >}}) and [Image Processing]({{< relref "content-management/image-processing" >}}) to get the full picture.
+These terms are connected, and you also need to read about [Page Resources]({{< relref "/content-management/page-resources" >}}) and [Image Processing]({{< relref "/content-management/image-processing" >}}) to get the full picture.
 
 {{% imgproc 1-featured Resize "300x" %}}
 The illustration shows 3 bundles. Note that the home page bundle cannot contain other content pages, but other files (images etc.) are fine.

content/en/news/0.45-relnotes/index.md

@@ -1,8 +1,8 @@
 
 ---
 date: 2018-07-22
-title: "0.45"
-description: "0.45"
+title: "Hugo 0.45: Revival of ref, relref and GetPage"
+description: "Hugo 0.45 adds relative page lookups, language support in ref/relref and several Hugo Pipes improvements."
 categories: ["Releases"]
 ---
 
@@ -15,7 +15,7 @@ Now you can simply do:
 {{ with .Site.GetPage "/blog/my-post.md" }}{{ .Title }}{{ end }}
 ```
 
-Or two get a section page:
+Or to get a section page:
 
 
 ```go-html-template

content/en/troubleshooting/build-performance.md

@@ -108,4 +108,4 @@ the memory usage per step, and the total memory allocations per step.
 To enable *step analysis*, use the `--stepAnalysis` option when running Hugo.
 
 
-[partialCached]:{{< ref "functions/partialCached.md" >}}
+[partialCached]:{{< ref "/functions/partialCached.md" >}}

netlify.toml

@@ -3,28 +3,28 @@ publish = "public"
 command = "hugo"
 
 [context.production.environment]
-HUGO_VERSION = "0.44"
+HUGO_VERSION = "0.45"
 HUGO_ENV = "production"
 HUGO_ENABLEGITINFO = "true"
 
 [context.split1]
 command = "hugo --enableGitInfo"
 
 [context.split1.environment]
-HUGO_VERSION = "0.44"
+HUGO_VERSION = "0.45"
 HUGO_ENV = "production"
 
 [context.deploy-preview]
 command = "hugo --buildFuture -b $DEPLOY_PRIME_URL"
 
 [context.deploy-preview.environment]
-HUGO_VERSION = "0.44"
+HUGO_VERSION = "0.45"
 
 [context.branch-deploy]
 command = "hugo -b $DEPLOY_PRIME_URL"
 
 [context.branch-deploy.environment]
-HUGO_VERSION = "0.44"
+HUGO_VERSION = "0.45"
 
 [context.next.environment]
 HUGO_ENABLEGITINFO = "true"