diff --git a/content/content-management/cross-references.md b/content/content-management/cross-references.md
index 7ee81f3db..358152672 100644
--- a/content/content-management/cross-references.md
+++ b/content/content-management/cross-references.md
@@ -96,8 +96,8 @@ More information about document unique identifiers and headings can be found [be
### Examples
-* `{{}}` => `http://example.com/blog/post/`
-* `{{}}` => `http://example.com/blog/post/#tldr:caffebad`
+* `{{}}` => `https://example.com/blog/post/`
+* `{{}}` => `https://example.com/blog/post/#tldr:caffebad`
* `{{}}` => `/blog/post/`
* `{{}}` => `/blog/post/#tldr:caffebad`
* `{{}}` => `#tldr:badcaffe`
diff --git a/content/content-management/menus.md b/content/content-management/menus.md
index 7c877afc8..364867c67 100644
--- a/content/content-management/menus.md
+++ b/content/content-management/menus.md
@@ -153,7 +153,7 @@ menu:
{{< /code >}}
{{% note %}}
-The URLs must be relative to the context root. If the `baseURL` is `http://example.com/mysite/`, then the URLs in the menu must not include the context root `mysite`. Using an absolute URL will overide the baseURL. If the value used for `URL` in the above example is `http://subdomain.example.com/`, the output will be `http://subdomain.example.com`.
+The URLs must be relative to the context root. If the `baseURL` is `https://example.com/mysite/`, then the URLs in the menu must not include the context root `mysite`. Using an absolute URL will overide the baseURL. If the value used for `URL` in the above example is `https://subdomain.example.com/`, the output will be `https://subdomain.example.com`.
{{% /note %}}
## Nesting
diff --git a/content/content-management/organization.md b/content/content-management/organization.md
index 33780c0eb..1ede7c0e5 100644
--- a/content/content-management/organization.md
+++ b/content/content-management/organization.md
@@ -34,20 +34,20 @@ While Hugo supports content nested at any level, the top levels (i.e. `content/<
.
└── content
└── about
- | └── _index.md // <- http://example.com/about/
+ | └── _index.md // <- https://example.com/about/
├── post
- | ├── firstpost.md // <- http://example.com/post/firstpost/
+ | ├── firstpost.md // <- https://example.com/post/firstpost/
| ├── happy
- | | └── ness.md // <- http://example.com/post/happy/ness/
- | └── secondpost.md // <- http://example.com/post/secondpost/
+ | | └── ness.md // <- https://example.com/post/happy/ness/
+ | └── secondpost.md // <- https://example.com/post/secondpost/
└── quote
- ├── first.md // <- http://example.com/quote/first/
- └── second.md // <- http://example.com/quote/second/
+ ├── first.md // <- https://example.com/quote/first/
+ └── second.md // <- https://example.com/quote/second/
```
## Path Breakdown in Hugo
-The following demonstrates the relationships between your content organization and the output URL structure for your Hugo website when it renders. These examples assume you are [using pretty URLs][pretty], which is the default behavior for Hugo. The examples also assume a key-value of `baseurl = "http://example.com"` in your [site's configuration file][config].
+The following demonstrates the relationships between your content organization and the output URL structure for your Hugo website when it renders. These examples assume you are [using pretty URLs][pretty], which is the default behavior for Hugo. The examples also assume a key-value of `baseurl = "https://example.com"` in your [site's configuration file][config].
### Index Pages: `_index.md`
@@ -76,7 +76,7 @@ At build, this will output to the following destination with the associated valu
⊢--------^---------⊣⊢-^-⊣
permalink
⊢----------^-------------⊣
-http://example.com/posts/index.html
+https://example.com/posts/index.html
```
### Single Pages in Sections
@@ -102,7 +102,7 @@ At the time Hugo builds your site, the content will be output to the following d
⊢--------^--------⊣⊢-^--⊣⊢-------^---------⊣
permalink
⊢--------------------^---------------------⊣
-http://example.com/posts/my-first-hugo-post/index.html
+https://example.com/posts/my-first-hugo-post/index.html
```
### Section with Nested Directories
@@ -120,7 +120,7 @@ To continue the example, the following demonstrates destination paths for a file
⊢--------^--------⊣ ⊢------^-----⊣⊢----^------⊣
permalink
⊢----------------------^-----------------------⊣
-http://example.com/events/chicago/lollapalooza/
+https://example.com/events/chicago/lollapalooza/
```
{{% note %}}
diff --git a/content/content-management/urls.md b/content/content-management/urls.md
index 262c73de2..29cd66e84 100644
--- a/content/content-management/urls.md
+++ b/content/content-management/urls.md
@@ -43,7 +43,7 @@ permalinks:
post = "/:year/:month/:title/"
{{< /code >}}
-Only the content under `post/` will have the new URL structure. For example, the file `content/post/sample-entry.md` with `date: 2017-02-27T19:20:00-05:00` in its front matter will render to `public/2017/02/sample-entry/index.html` at build time and therefore be reachable at `http://example.com/2013/11/sample-entry/`.
+Only the content under `post/` will have the new URL structure. For example, the file `content/post/sample-entry.md` with `date: 2017-02-27T19:20:00-05:00` in its front matter will render to `public/2017/02/sample-entry/index.html` at build time and therefore be reachable at `https://example.com/2013/11/sample-entry/`.
### Permalink Configuration Values
@@ -147,11 +147,11 @@ Assuming a `baseURL` of `example.com`, the contents of the auto-generated alias
- http://example.com/posts/my-intended-url
-
+ https://example.com/posts/my-intended-url
+
-
+
```
@@ -200,15 +200,15 @@ See [Content Organization][contentorg] for more details on paths.
.
└── content
└── about
- | └── _index.md // <- http://example.com/about/
+ | └── _index.md // <- https://example.com/about/
├── post
- | ├── firstpost.md // <- http://example.com/post/firstpost/
+ | ├── firstpost.md // <- https://example.com/post/firstpost/
| ├── happy
- | | └── ness.md // <- http://example.com/post/happy/ness/
- | └── secondpost.md // <- http://example.com/post/secondpost/
+ | | └── ness.md // <- https://example.com/post/happy/ness/
+ | └── secondpost.md // <- https://example.com/post/secondpost/
└── quote
- ├── first.md // <- http://example.com/quote/first/
- └── second.md // <- http://example.com/quote/second/
+ ├── first.md // <- https://example.com/quote/first/
+ └── second.md // <- https://example.com/quote/second/
```
Here's the same organization run with `hugo --uglyURLs`:
@@ -217,15 +217,15 @@ Here's the same organization run with `hugo --uglyURLs`:
.
└── content
└── about
- | └── _index.md // <- http://example.com/about/index.html
+ | └── _index.md // <- https://example.com/about/index.html
├── post
- | ├── firstpost.md // <- http://example.com/post/firstpost.html
+ | ├── firstpost.md // <- https://example.com/post/firstpost.html
| ├── happy
- | | └── ness.md // <- http://example.com/post/happy/ness.html
- | └── secondpost.md // <- http://example.com/post/secondpost.html
+ | | └── ness.md // <- https://example.com/post/happy/ness.html
+ | └── secondpost.md // <- https://example.com/post/secondpost.html
└── quote
- ├── first.md // <- http://example.com/quote/first.html
- └── second.md // <- http://example.com/quote/second.html
+ ├── first.md // <- https://example.com/quote/first.html
+ └── second.md // <- https://example.com/quote/second.html
```
@@ -233,7 +233,7 @@ Here's the same organization run with `hugo --uglyURLs`:
By default, all relative URLs encountered in the input are left unmodified, e.g. `/css/foo.css` would stay as `/css/foo.css`. The `canonifyURLs` field in your site `config` has a default value of `false`.
-By setting `canonifyURLs` to `true`, all relative URLs would instead be *canonicalized* using `baseURL`. For example, assuming you have `baseURL = https://example.com/`, the relative URL `/css/foo.css` would be turned into the absolute URL `http://example.com/css/foo.css`.
+By setting `canonifyURLs` to `true`, all relative URLs would instead be *canonicalized* using `baseURL`. For example, assuming you have `baseURL = https://example.com/`, the relative URL `/css/foo.css` would be turned into the absolute URL `https://example.com/css/foo.css`.
Benefits of canonicalization include fixing all URLs to be absolute, which may aid with some parsing tasks. Note, however, that all modern browsers handle this on the client without issue.
diff --git a/content/contribute/themes.md b/content/contribute/themes.md
index dc8bddc3a..7055e94e8 100644
--- a/content/contribute/themes.md
+++ b/content/contribute/themes.md
@@ -64,7 +64,7 @@ name = ""
license = "MIT"
licenselink = "https://github.com///blob/master/LICENSE.md"
description = ""
-homepage = "http://example.com/"
+homepage = "https://example.com/"
tags = []
features = []
min_version = 0.19
diff --git a/content/functions/abslangurl.md b/content/functions/abslangurl.md
index 41903c61d..8a6f49854 100644
--- a/content/functions/abslangurl.md
+++ b/content/functions/abslangurl.md
@@ -20,9 +20,9 @@ aliases: []
Both `absLangURL` and [`relLangURL`](/functions/rellangurl/) are similar to their [`absURL`](/functions/absurl/) and [`relURL`](/functions/relurl) relatives but will add the correct language prefix when the site is configured with more than one language.
-So for a site `baseURL` set to `http://example.com/hugo/` and the current language is `en`:
+So for a site `baseURL` set to `https://example.com/hugo/` and the current language is `en`:
```
-{{ "blog/" | absLangURL }} → "http://example.com/hugo/en/blog/"
+{{ "blog/" | absLangURL }} → "https://example.com/hugo/en/blog/"
{{ "blog/" | relLangURL }} → "/hugo/en/blog/"
```
diff --git a/content/functions/absurl.md b/content/functions/absurl.md
index 40cc9111c..2e03ca49d 100644
--- a/content/functions/absurl.md
+++ b/content/functions/absurl.md
@@ -18,10 +18,10 @@ deprecated: false
aliases: []
---
-Both `absURL` and `relURL` consider the configured value of `baseURL` in your site's [`config` file][configuration]. Given a `baseURL` set to `http://example.com/hugo/`:
+Both `absURL` and `relURL` consider the configured value of `baseURL` in your site's [`config` file][configuration]. Given a `baseURL` set to `https://example.com/hugo/`:
```
-{{ "mystyle.css" | absURL }} → "http://example.com/hugo/mystyle.css"
+{{ "mystyle.css" | absURL }} → "https://example.com/hugo/mystyle.css"
{{ "mystyle.css" | relURL }} → "/hugo/mystyle.css"
{{ "http://gohugo.io/" | relURL }} → "http://gohugo.io/"
{{ "http://gohugo.io/" | absURL }} → "http://gohugo.io/"
diff --git a/content/functions/math.md b/content/functions/math.md
index 60b801dfa..6375ad738 100644
--- a/content/functions/math.md
+++ b/content/functions/math.md
@@ -38,7 +38,7 @@ You can also use the `add` function with strings. You may like this functionalit
For example, social media sharing with [Twitter Cards][cards] requires the following `meta` link in your site's `` to display Twitter's ["Summary Card with Large Image"][twtsummary]:
```
-
+
```
Let's assume you have an `image` field in the front matter of each of your content files:
diff --git a/content/functions/relLangURL.md b/content/functions/relLangURL.md
index 08f4511fb..2df271746 100644
--- a/content/functions/relLangURL.md
+++ b/content/functions/relLangURL.md
@@ -20,10 +20,10 @@ aliases: []
`absLangURL` and `relLangURL` functions are similar to their [`absURL`](/functions/absurl/) and [`relURL`](/functions/relurl/) relatives but will add the correct language prefix when the site is configured with more than one language. (See [Configuring Multilingual][multiliconfig].)
-So for a site `baseURL` set to `http://example.com/hugo/` and the current language is `en`:
+So for a site `baseURL` set to `https://example.com/hugo/` and the current language is `en`:
```
-{{ "blog/" | absLangURL }} → "http://example.com/hugo/en/blog/"
+{{ "blog/" | absLangURL }} → "https://example.com/hugo/en/blog/"
{{ "blog/" | relLangURL }} → "/hugo/en/blog/"
```
diff --git a/content/functions/relurl.md b/content/functions/relurl.md
index 2760d10c8..085c344f5 100644
--- a/content/functions/relurl.md
+++ b/content/functions/relurl.md
@@ -18,10 +18,10 @@ deprecated: false
aliases: []
---
-Both `absURL` and `relURL` consider the configured value of `baseURL` in your site's [`config` file][configuration]. Given a `baseURL` set to `http://example.com/hugo/`:
+Both `absURL` and `relURL` consider the configured value of `baseURL` in your site's [`config` file][configuration]. Given a `baseURL` set to `https://example.com/hugo/`:
```
-{{ "mystyle.css" | absURL }} → "http://example.com/hugo/mystyle.css"
+{{ "mystyle.css" | absURL }} → "https://example.com/hugo/mystyle.css"
{{ "mystyle.css" | relURL }} → "/hugo/mystyle.css"
{{ "http://gohugo.io/" | relURL }} → "http://gohugo.io/"
{{ "http://gohugo.io/" | absURL }} → "http://gohugo.io/"
diff --git a/content/getting-started/quick-start.md b/content/getting-started/quick-start.md
index f7413ac3b..5683087d6 100644
--- a/content/getting-started/quick-start.md
+++ b/content/getting-started/quick-start.md
@@ -118,7 +118,7 @@ Your new site already looks great, but you will want to tweak it a little before
Open up `config.toml` in a text editor:
```
-baseURL = "http://example.org/"
+baseURL = "https://example.org/"
languageCode = "en-us"
title = "My New Hugo Site"
theme = "ananke"
diff --git a/content/templates/output-formats.md b/content/templates/output-formats.md
index 66958ff1d..db368cbe4 100644
--- a/content/templates/output-formats.md
+++ b/content/templates/output-formats.md
@@ -71,7 +71,7 @@ isPlainText = true
protocol = "bep://"
```
-The above example is fictional, but if used for the homepage on a site with `baseURL` `http://example.org`, it will produce a plain text homepage with the URL `bep://example.org/myindex.enr`.
+The above example is fictional, but if used for the homepage on a site with `baseURL` `https://example.org`, it will produce a plain text homepage with the URL `bep://example.org/myindex.enr`.
### Configure Output Formats
diff --git a/content/variables/site.md b/content/variables/site.md
index 68b943388..447a21fc3 100644
--- a/content/variables/site.md
+++ b/content/variables/site.md
@@ -109,7 +109,7 @@ The following is a list of site-level (aka "global") variables. Many of these va
The following `config.toml` defines a site-wide param for `description`:
```
-baseURL = "http://yoursite.example.com/"
+baseURL = "https://yoursite.example.com/"
[params]
description = "Tesla's Awesome Hugo Site"