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

Merge commit '346b60358dd8ec2ca228e6635bff9d7914b398b7'

Browse Source
This commit is contained in:
Bjørn Erik Pedersen
2025-01-23 09:47:46 +01:00
parent 7f0f50b133 346b60358d
commit 43307b07f8
384 changed files with 3305 additions and 3271 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -53,7 +53,7 @@ The [`hugo`] command builds your site, publishing the files to the `public` dire
{{% note %}}
Hugo does not clear the `public` directory before building your site. Existing files are overwritten, but not deleted. This behavior is intentional to prevent the inadvertent removal of files that you may have added to the `public` directory after the build.
Depending on your needs, you may wish to manually clear the contents of the public directory before every build.
Depending on your needs, you may wish to manually clear the contents of the `public` directory before every build.
{{% /note %}}
## Draft, future, and expired content
@@ -68,11 +68,10 @@ Hugo allows you to set `draft`, `date`, `publishDate`, and `expiryDate` in the [
{{< new-in 0.123.0 >}}
{{% note %}}
Hugo publishes descendants of draft, future, and expired [node] pages. To prevent publication of these descendants, use the [`cascade`] front matter field to cascade [build options] to the descendant pages.
Hugo publishes descendants of draft, future, and expired [node](g) pages. To prevent publication of these descendants, use the [`cascade`] front matter field to cascade [build options] to the descendant pages.
[build options]: /content-management/build-options/
[`cascade`]: /content-management/front-matter/#cascade-field
[node]: /getting-started/glossary/#node
{{% /note %}}
You can override the default behavior when running `hugo` or `hugo server` with command line flags:
@@ -124,7 +123,7 @@ hugo server --navigateToChanged
## Deploy your site
{{% note %}}
As noted above, Hugo does not clear the public directory before building your site. Manually clear the contents of the public directory before each build to remove draft, expired, and future content.
As noted above, Hugo does not clear the `public` directory before building your site. Manually clear the contents of the `public` directory before each build to remove draft, expired, and future content.
{{% /note %}}
When you are ready to deploy your site, run:
@@ -133,7 +132,7 @@ When you are ready to deploy your site, run:
hugo
```
This builds your site, publishing the files to the public directory. The directory structure will look something like this:
This builds your site, publishing the files to the `public` directory. The directory structure will look something like this:
```text
public/
@@ -159,7 +158,7 @@ Most of our users deploy their sites using a CI/CD workflow, where a push[^1] to
Learn more in the [hosting and deployment] section.
[^1]: The Git repository contains the entire project directory, typically excluding the public directory because the site is built _after_ the push.
[^1]: The Git repository contains the entire project directory, typically excluding the `public` directory because the site is built _after_ the push.
[`--destination`]: /commands/hugo/#options
[`hugo server`]: /commands/hugo_server/