mirror/hugo
1
0
Fork 0
mirror of https://github.com/gohugoio/hugo.git synced 2025-08-25 22:00:58 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge commit 'aa5ac36a3eb68b86c803caec703869efefc8447e'

Browse Source
This commit is contained in:
Bjørn Erik Pedersen
2021-10-31 13:53:55 +01:00
parent 3a977485eb aa5ac36a3e
commit 4b36498a85
162 changed files with 80 additions and 636 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/content/en/getting-started/configuration.md
View File

@@ -319,7 +319,7 @@ Default number of elements per page in [pagination](/templates/pagination/).
**Default value:** "page"
The path element used during pagination (https://example.com/page/2).
The path element used during pagination (`https://example.com/page/2`).
### permalinks
See [Content Management](/content-management/urls/#permalinks).
@@ -346,7 +346,7 @@ Enable this to make all relative URLs relative to content root. Note that this d
**Default value:** "ERROR"
When using `ref` or `relref` to resolve page links and a link cannot resolved, it will be logged with this logg level. Valid values are `ERROR` (default) or `WARNING`. Any `ERROR` will fail the build (`exit -1`).
When using `ref` or `relref` to resolve page links and a link cannot resolved, it will be logged with this log level. Valid values are `ERROR` (default) or `WARNING`. Any `ERROR` will fail the build (`exit -1`).
### refLinksNotFoundURL
URL to be used as a placeholder when a page reference cannot be found in `ref` or `relref`. Is used as-is.
@@ -450,7 +450,7 @@ noJSConfigInAssets {{< new-in "0.78.0" >}}
{{< new-in "0.67.0" >}}
This is only relevant when running `hugo server`, and it allows to set HTTP headers during development, which allows you to test out your Content Security Policy and similar. The configuration format matches [Netlify's](https://docs.netlify.com/routing/headers/#syntax-for-the-netlify-configuration-file) with slighly more powerful [Glob matching](https://github.com/gobwas/glob):
This is only relevant when running `hugo server`, and it allows to set HTTP headers during development, which allows you to test out your Content Security Policy and similar. The configuration format matches [Netlify's](https://docs.netlify.com/routing/headers/#syntax-for-the-netlify-configuration-file) with slightly more powerful [Glob matching](https://github.com/gobwas/glob):
{{< code-toggle file="config">}}

4
docs/content/en/getting-started/quick-start.md
View File

@@ -23,7 +23,7 @@ This quick start uses `macOS` in the examples. For instructions about how to ins
It is recommended to have [Git installed](https://git-scm.com/downloads) to run this tutorial.
For other approaches learning Hugo like book or a video tutorial refer to the [external learning resources](/getting-started/external-learning-resources/) page.
For other approaches to learning Hugo (like books or video tutorials), refer to the [external learning resources](/getting-started/external-learning-resources/) page.
{{% /note %}}
## Step 1: Install Hugo
@@ -140,7 +140,7 @@ Press Ctrl+C to stop
**Navigate to your new site at [http://localhost:1313/](http://localhost:1313/).**
Feel free to edit or add new content and simply refresh in browser to see changes quickly (You might need to force refresh in webbrowser, something like Ctrl-R usually works).
Feel free to edit or add new content and simply refresh in browser to see changes quickly. (You might need to force refresh your web browser, something like Ctrl-R usually works.)
## Step 6: Customize the Theme

2
docs/content/en/getting-started/usage.md
View File

@@ -176,7 +176,7 @@ Fortunately Hugo has an easy, embedded and simple solution for this. It's the fl
LiveReload works by injecting JavaScript into the pages Hugo generates. The script creates a connection from the browser's web socket client to the Hugo web socket server.
LiveReload is awesome for development. However, some Hugo users may use `hugo server` in production to instantly display updated content. The following methods make it easy to disable LiveReload:
The following methods make it easy to disable LiveReload:
```
hugo server --watch=false