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
Copy file name to clipboardExpand all lines: .github/pull_request_template.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,14 +23,13 @@ Before merging a pull request, run through this checklist and mark each as compl
23
23
24
24
-[ ] I have read the [contributing guidelines](https://github.com/nginx/documentation/blob/main/CONTRIBUTING.md)
25
25
-[ ] I have signed the [F5 Contributor License Agreement (CLA)](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md)
26
+
-[ ] I have rebased my branch onto main
27
+
-[ ] I have ensured my PR is targeting the main branch and pulling from my branch from my own fork
28
+
-[ ] I have ensured that the commit messages adhere to [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#summary)
26
29
-[ ] I have ensured that documentation content adheres to [the style guide](https://github.com/nginx/documentation/blob/main/templates/style-guide.md)
27
-
-[ ] If the change involves potentially sensitive changes, I have assessed the possible impact
30
+
-[ ] If the change involves potentially sensitive changes[^1], I have assessed the possible impact
28
31
-[ ] If applicable, I have added tests that prove my fix is effective or that my feature works
29
-
-[ ] If applicable, I have checked that any relevant tests pass after adding my changes
30
-
-[ ] I have updated any relevant documentation ([`README.md`](https://github.com/nginx/documentation/blob/main/README.md) and [`CHANGELOG.md`](https://github.com/nginx/documentation/blob/main/CHANGELOG.md)
31
-
-[ ] I have rebased my branch onto main
32
-
-[ ] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork
33
-
34
-
Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation.
32
+
-[ ] I have ensured that existing tests pass after adding my changes
33
+
-[ ] If applicable, I have updated [`README.md`](https://github.com/nginx/documentation/blob/main/README.md) and [`CHANGELOG.md`](https://github.com/nginx/documentation/blob/main/CHANGELOG.md)
35
34
36
-
Please refer to [our style guide](https://github.com/nginx/documentation/blob/main/templates/style-guide.md) for guidance about placeholder content.
35
+
[^1]: Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to [our style guide](https://github.com/nginx/documentation/blob/main/templates/style-guide.md) for guidance about placeholder content.
Copy file name to clipboardExpand all lines: CONTRIBUTING_DOCS.md
+30-6Lines changed: 30 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,14 +16,13 @@ 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.2](https://github.com/gohugoio/hugo/releases/tag/v0.134.2) in production.
20
-
21
19
22
20
Although not a strict requirement, markdown-link-check is also used in documentation development.
23
21
24
22
If you have [Docker](https://www.docker.com/get-started/) installed, there are fallbacks for all requirements in the [Makefile](Makefile), meaning you don't need to install them.
@@ -35,7 +34,11 @@ The configuration files are as follows:
35
34
36
35
## Local Docs Development
37
36
38
-
To build the documentation locally, use the `make` command in the documentation folder with these targets:
37
+
To build the documentation locally, use the `make` command in the documentation folder. First make sure you have the latest version of our Hugo theme with:
38
+
39
+
`make hugo-update`
40
+
41
+
Once you've updated the theme, you can use these targets:
39
42
40
43
```text
41
44
make watch - Runs a local Hugo server, allowing for changes to be previewed in a browser.
@@ -64,7 +67,7 @@ We have templates for the following types of documentation:
64
67
65
68
## How to format docs
66
69
67
-
### Basic markdown formatting
70
+
### Basic Markdown formatting
68
71
69
72
There are multiple ways to format text: for consistency and clarity, these are our conventions:
70
73
@@ -133,12 +136,14 @@ Supported callouts:
133
136
-`caution`
134
137
-`warning`
135
138
136
-
You can also create custom callouts using the `call-out` shortcode `{{< call-out "type" "header" "font-awesome icon >}}`. For example:
139
+
You can also create custom callouts using the `call-out` shortcode `{{< call-out "type position" "header" "font-awesome icon >}}`. For example:
137
140
138
141
```md
139
-
{{<call-out "important" "JWT file required for upgrade" "fa fa-exclamation-triangle">}}
142
+
{{<call-out "important side-callout" "JWT file required for upgrade" "fa fa-exclamation-triangle">}}
140
143
```
141
144
145
+
By default, all custom callouts are included inline, unless you add `side-callout` which places the callout to the right of the content.
146
+
142
147
Here are some other shortcodes:
143
148
144
149
-`fa`: Inserts a Font Awesome icon
@@ -152,6 +157,25 @@ Here are some other shortcodes:
152
157
-`readfile`: Include the content of another file in the current file, which can be in an arbitrary location.
153
158
-`bootstrap-table`: formats a table using Bootstrap classes; accepts any bootstrap table classes as additional arguments, e.g. `{{< bootstrap-table "table-bordered table-hover" }}`
154
159
160
+
### How to use Hugo includes
161
+
162
+
As mentioned above, [Hugo includes](https://gohugo.io/contribute/documentation/#include) are a custom shortcode that allows you to reference reusable content stored in the [`/content/includes` directory](https://github.com/nginx/documentation/tree/main/content/includes).
163
+
164
+
For example, if the [`controller/add-existing-instance.md`](https://github.com/nginx/documentation/blob/main/content/includes/controller/add-existing-instance.md) file contains instructions on adding an instance to the NGINX Controller, you can reuse it on multiple pages by adding:
165
+
166
+
```md
167
+
{{< include "controller/add-existing-instance.md" >}}
168
+
```
169
+
170
+
The `controller/add-existing-instance.md` file is included in the following pages on the NGINX Docs Site:
171
+
172
+
-[Add an NGINX App Protect Instance](https://github.com/nginx/documentation/blob/main/content/controller/infrastructure/instances/add-nap-instance.md?plain=1#L35)
173
+
-[Manage Your NGINX Instances](https://github.com/nginx/documentation/blob/main/content/controller/infrastructure/instances/manage-instances.md?plain=1#L29)
174
+
-[Trial NGINX Controller with NGINX Plus](https://github.com/nginx/documentation/blob/main/content/controller/admin-guides/install/try-nginx-controller.md?plain=1#L277)
175
+
-[Trial NGINX Controller with App Security](https://github.com/nginx/documentation/blob/main/content/controller/admin-guides/install/try-nginx-controller-app-sec.md?plain=1#L290)
176
+
177
+
This ensures that content is defined once and referenced in multiple places without duplication.
178
+
155
179
## Linting
156
180
157
181
To run the markdownlint check, run the following command, which uses the .markdownlint.yaml file to specify rules. For `<content>`, specify the path to your Markdown files:
0 commit comments