@@ -16,7 +16,7 @@ If you're an employee of F5/NGINX, also read [For F5/NGINX Employees](./F5-NGINX
16
16
You will need to install Hugo _ or_ Docker to build and preview docs in your local development environment.
17
17
Refer to the [ Hugo installation instructions] ( https://gohugo.io/getting-started/installing/ ) for more information.
18
18
19
- ** NOTE** : We are currently running [ Hugo v0.134.3 ] ( https://github.com/gohugoio/hugo/releases/tag/v0.134.3 ) in production.
19
+ ** NOTE** : We are currently running [ Hugo v0.134.2 ] ( https://github.com/gohugoio/hugo/releases/tag/v0.134.2 ) in production.
20
20
21
21
22
22
Although not a strict requirement, markdown-link-check is also used in documentation development.
@@ -38,11 +38,9 @@ The configuration files are as follows:
38
38
To build the documentation locally, use the ` make ` command in the documentation folder with these targets:
39
39
40
40
``` text
41
- make docs - Builds the documentation.
42
- make watch - Runs a Hugo server to automatically preview changes on a local browser. Use this if you want to preview
43
- the documentation locally before submitting a PR.
44
- make drafts - Runs a Hugo server, and displays documentation marked as drafts on a local browser. By default, drafts
45
- are not displayed.
41
+ make watch - Runs a local Hugo server, allowing for changes to be previewed in a browser.
42
+ make drafts - Runs a local Hugo server similar to the `watch` target, but displays documents marked with `draft: true` in their metadata.
43
+ make docs - Builds the documentation in the local `public/` directory.
46
44
make hugo-get - Updates the go module file with the latest version of the theme.
47
45
make hugo-tidy - Removes unnecessary dependencies from the go module file.
48
46
make hugo-update - Runs the hugo-get and hugo-tidy targets in sequence.
0 commit comments