Merge commit 'f147b5c53eda15982e0fe762847532eeddb7485f'

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

@@ -115,7 +115,7 @@ With the above, the two sites will be generated into `public` with their own roo
 ```bash
 public
 ├── en
-└── no
+└── fr
 ```
 
 **All URLs (i.e `.Permalink` etc.) will be generated from that root. So the English home page above will have its `.Permalink` set to `https://example.com/`.**

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

@@ -105,7 +105,7 @@ You can show content summaries with the following code. You could use the follow
 {{ end }}
 {{< /code >}}
 
-Note how the `.Truncated` boolean valuable may be used to hide the "Read More..." link when the content is not truncated; i.e., when the summary contains the entire article.
+Note how the `.Truncated` boolean variable value may be used to hide the "Read More..." link when the content is not truncated; i.e., when the summary contains the entire article.
 
 [org]: /content-management/formats/
 [pagevariables]: /variables/page/

docs/content/en/hosting-and-deployment/hosting-on-aws-amplify.md

@@ -40,4 +40,6 @@ AWS Amplify is a combination of client library, CLI toolchain, and a Console for
 1.  Accept the default build settings. The Amplify Console automatically detects your Hugo build settings and output directory.
    ![Hugo Amplify](/images/hosting-and-deployment/hosting-on-aws-amplify/amplify-build-settings.png)
 
-1. Review your changes and then choose **Save and deploy**. The Amplify Console will pull code from your repository, build changes to the backend and frontend, and deploy your build artifacts at `https://master.unique-id.amplifyapp.com`. Bonus: Screenshots of your app on different devices to find layout issues.
+1. Review your changes and then choose **Save and deploy**. The Amplify Console will pull code from your repository, build changes to the backend and frontend, and deploy your build artifacts at `https://master.unique-id.amplifyapp.com`. Bonus: Screenshots of your app on different devices to find layout issues.
+
+[Quick Start]: /getting-started/quick-start/

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

@@ -1,16 +1,14 @@
 
 ---
 date: 2019-04-20
-title: "0.55.3"
+title: "Hugo 0.55.3: A Few More Bug Fixes!"
-description: "0.55.3"
+description: "To wrap up this Eeaster, here is one more patch release with some important fixes."
 categories: ["Releases"]
 images:
 - images/blog/hugo-bug-poster.png
 
 ---
 
-	
-
 This is a bug-fix release with a couple of important fixes.
 
 

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

@@ -1,8 +1,8 @@
 
 ---
 date: 2019-04-25
-title: "0.55.4"
+title: "Hugo 0.55.4: Some Bug Fixes"
-description: "0.55.4"
+description: "A couple of more bug fixes."
 categories: ["Releases"]
 images:
 - images/blog/hugo-bug-poster.png

docs/content/en/showcase/pharmaseal/bio.md

@@ -0,0 +1,7 @@
+PHARMASEAL began in 2016 with the purpose of disrupting the Clinical Trials Management market through continuos validation and intergration
+
+We've been using **Hugo + Webpack + Netlify** to provide a scalable, modular design for the website, complete with Forestry building blocks to quickly be able to generate engagement pages.
+
+The site is built by:
+
+- [Roboto Studio](https://roboto.studio)

docs/content/en/showcase/pharmaseal/index.md

@@ -0,0 +1,37 @@
+---
+
+title: PHARMASEAL
+date: 2019-04-29
+
+description: "Pharmaseal website developed using Hugo, Forestry, hosted and deployed by Netlify."
+
+# The URL to the site on the internet.
+siteURL: https://pharmaseal.co/
+
+# Link to the site's Hugo source code if public and you can/want to share.
+# Remove or leave blank if not needed/wanted.
+
+
+# Add credit to the article author. Leave blank or remove if not needed/wanted.
+byline: "[Roboto Studio](https://roboto.studio), Jonathan Alford"
+
+---
+
+
+We wanted to shake the status quo with PHARMASEAL, opting for a fast and scalable website built with Hugo instead of slower monolithic systems the competitors were using.
+
+We had two goals:
+
+**Make it fast**
+
+We wanted to optimise the site as much as possible, so we opted for using Cloudinary, enabling us to take advantage of on-the-fly image manipulation, and thanks to the sheer speed of static sites, we achieved a perfect optimisation score with Google audits.
+
+Because we're hosting the site through Netlify and our target audience is in America, we are taking advantage of Netlify edge (Their alternative to a CDN). We're talking blazing fast.
+
+**Make it easy**
+
+We're big fans of simplicity, and that's what we delivered with the Forestry building blocks. Every element on the site is built with building blocks in mind, allowing PHARMASEAL to generate multiple pages in the blink of an eye.
+
+PHARMASEAL have found Forestry CMS combined with HUGO to be so effective at producing fast, purpose driven pages, that we have worked with them to add even more blocks in a scalable, modular fashion.
+
+**TLDR:** We're blown away with HUGO, the sheer speed, scalability and deployment possibilities with Netlify is the 💣

docs/netlify.toml

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