You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit updates the documentation Makefile and README, removing
references to Netlify and clarifying the usage of the Makefile. This is
part of an effort to ensure they remain consistent across all NGINX
repositories.
Copy file name to clipboardExpand all lines: site/README.md
+15-16Lines changed: 15 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -38,36 +38,35 @@ The documentation is published from the latest public release branch. If your ch
38
38
39
39
## Developing documentation locally
40
40
41
-
To build the documentation locally, run the `make` command inside this `/site/` directory:
41
+
To build the documentation locally, use the `make` command in the documentation folder with these targets:
42
42
43
43
```text
44
-
make docs - Builds the documentation set with the output as the '/public' directory
45
-
make clean - Removes the local '/public/' directory
46
-
make watch - Starts a local Hugo server for live previews
47
-
make watch-drafts - Starts a local Hugo server for live previews, including documentation marked with 'draft: true'
48
-
make link-check - Check for any broken links in the documentation
49
-
make lint-markdown - Runs markdownlint to identify possible markdown formatting issues
44
+
make docs - Builds the documentation
45
+
make watch - Runs a local Hugo server to automatically preview changes
46
+
make drafts - Runs a local Hugo server, and displays documentation marked as drafts
47
+
make clean - Removes the output 'public' directory created by Hugo
48
+
make hugo-get - Updates the go module file with the latest version of the theme
49
+
make hugo-tidy - Removes unnecessary dependencies from the go module file
50
+
make hugo-update - Runs the hugo-get and hugo-tidy targets in sequence
51
+
make lint-markdown - Runs markdownlint on the content folder
52
+
make link-check - Runs markdown-link-check on all Markdown files
50
53
```
51
54
52
-
The `watch` options automatically reload the Hugo server, allowing you to view updates as you work.
53
-
54
-
> **Note**: The documentation uses build environments to control the baseURL used for things like internal references and static resources. The configuration for each environment can be found in the `config` directory. When running Hugo you can specify the environment and baseURL, but it's unnecessary.
55
-
56
55
## Adding new documentation
57
56
58
-
### Using Hugo to generate a new documentation file
57
+
### Generate a new documentation file using Hugo
59
58
60
-
To create a new documentation file with the pre-configured Hugo front-matter for the task template, run the following command inside this `/site` directory:
59
+
To create a new documentation file containing the pre-configured Hugo front-matter with the task template, **run the following command in the documentation directory**:
61
60
62
-
`hugo new <SECTIONNAME>/<FILENAME>.md`
61
+
`hugo new <SECTIONNAME>/<FILENAME>.<FORMAT>`
63
62
64
63
For example:
65
64
66
65
```shell
67
66
hugo new getting-started/install.md
68
67
```
69
68
70
-
The default template (task) should be used for most pages. For other content templates, you can use the `--kind` flag:
69
+
The default template -- task -- should be used for most documentation. To create documentation using the other content templates, you can use the `--kind` flag:
71
70
72
71
```shell
73
72
hugo new tutorials/deploy.md --kind tutorial
@@ -125,7 +124,7 @@ Use the `img` [shortcode](#using-hugo-shortcodes) to add images into your docume
125
124
126
125
### Using Hugo shortcodes
127
126
128
-
[Hugo shortcodes](/docs/themes/f5-hugo/layouts/shortcodes/) are used to format callouts, add images, and reuse content across different pages.
127
+
[Hugo shortcodes](https://github.com/nginxinc/nginx-hugo-theme/tree/main/layouts/shortcodes) are used to format callouts, add images, and reuse content across different pages.
0 commit comments