feat: Update issue templates & process docs

This commit updates the issue templates into the repository, converting
them from plain Markdown templates to interactive forms. It also updates
the process documentation, re-organising them into topic groups and
adding guidance on the level of desired detail for requests.

Author: ADubhlaoich

.github/ISSUE_TEMPLATE/1-general_request.md

@@ -0,0 +1,36 @@
+---
+name: General request
+about: This template is for recording general documentation requests
+title: ""
+labels: "enhancement"
+projects: ["nginx/22"]
+assignees: ""
+---
+
+https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms
+
+*Remove italicized directions as relevant to reduce noise in the issue description.*
+
+### What would you like the documentation team to work on?
+
+*Please describe your request with as much detail as possible.*
+
+### Who is the person directly responsible for initiating this request?
+
+*Name the specific stakeholders for this request.*
+
+### Is this request part of a larger initiative or project?
+
+*Mention the project related to the broader impact this request relates to.*
+
+### Is there important information necessary to contextualise this request?
+
+*If the request is particularly large, you may want to organise a meeting before filing an issue.*
+
+### Does this request have a due date?
+
+*You should name any specific date you have in mind for this request, or any dependencies/blockers that would determine it.*
+
+### Any additional information
+
+*Add any remaining detail for this request not covered by the above questions.*

.github/ISSUE_TEMPLATE/1-general_request.yml

@@ -0,0 +1,44 @@
+name: General request
+description: Make a general documentation request.
+title: "[Request]: "
+body:
+  - type: textarea
+    id: what-work
+    label: What would you like the documentation team to work on?
+    description: Please describe your request with as much detail as possible.
+  - type: dropdown
+    id: what-product
+    label: Which product or products does this relate to?
+    description: You can figure this out based on page URL
+    multiple: true
+    options:
+      - F5 DoS for NGINX
+      - F5 WAF for NGINX
+      - NGINX Agent
+      - NGINXaaS for Azure
+      - NGINX Gateway Fabric
+      - NGINX Ingress Controller
+      - NGINX Instance Manager
+      - NGINX One Console
+      - NGINX Plus
+      - Other
+  - type: textarea
+    id: direct-responsibility
+    label: Who is the person directly responsible for initiating this request?
+    description: Name the specific person that made this request.
+  - type: textarea
+    id: request-scope
+    label: Is this request part of a larger initiative or project?
+    description: If it is, name the project the request relates to
+  - type: textarea
+    id: request-constraints
+    label: Are there important constraints for this request?
+    description: If the constraints are particularly complex, you may wish to organise a meeting instead of filing a request
+  - type: textarea
+    id: request-deadline
+    label: Does this request have a due date?
+    description: You should name any specific date you have in mind for this request, or any dependencies/blockers that would determine it.
+  - type: textarea
+    id: additional-information
+    label: Any additional information
+    description: Add any remaining detail for this request not covered by the above questions.

…thub/ISSUE_TEMPLATE/1-feature_request.md …thub/ISSUE_TEMPLATE/2-feature_request.md.github/ISSUE_TEMPLATE/1-feature_request.md renamed to .github/ISSUE_TEMPLATE/2-feature_request.md .github/ISSUE_TEMPLATE/1-feature_request.md renamed to .github/ISSUE_TEMPLATE/2-feature_request.md

@@ -34,14 +34,14 @@ If you'd like to discuss something NGINX-related that doesn't involve documentat
 
 ## Submit a pull request
 
-Before making documentation changes, you should view the [documentation style guide](/documentation/style-guide.md) and [Managing content with Hugo](/documentation/writing-hugo.md).
+Before making documentation changes, you should view the [documentation style guide](/documentation/style-guide.md) and [Managing content with Hugo](/documentation/hugo-content.md).
 
 To understand how we use Git in this repository, read our [Git conventions](/documentation/git-conventions.md) documentation.
 
 The broad workflow is as follows:
 
 - Fork the NGINX repository
-  - If you're an F5/NGINX user, you can work from a clone
+  - If you're an F5/NGINX user, you can branch directly with a clone
 - Create a branch
 - Implement your changes in your branch
 - Submit a pull request (PR) when your changes are ready for review
@@ -53,10 +53,9 @@ Alternatively, you're welcome to suggest improvements to highlight problems with
 To ensure a balance between work carried out by the NGINX team while encouraging community involvement on this project, we use the following
 issue lifecycle:
 
-- A new issue is created by a community member
-- An owner on the NGINX team is assigned to the issue; this owner shepherds the issue through the subsequent stages in the issue lifecycle
-- The owner assigns one or more [labels](https://github.com/nginxinc/oss-docs/issues/labels) to the issue
-- The owner, in collaboration with the community member, determines what milestone to attach to an issue. They may be milestones correspond to product releases
+- A new issue is created by 
+- A maintainer from the F5 team is assigned to the issue; this maintainer shepherds the issue through the subsequent stages in the issue lifecycle
+- The maintainer assigns one or more [labels](https://github.com/nginx/documentation/labels) to the issue
 
 ## Additional NGINX documentation
 

.github/ISSUE_TEMPLATE/2-bug_report.md .github/ISSUE_TEMPLATE/3-bug_report.md.github/ISSUE_TEMPLATE/2-bug_report.md renamed to .github/ISSUE_TEMPLATE/3-bug_report.md

@@ -16,7 +16,7 @@ If you're interested in contributing to the [NGINX documentation website](https:
 - [Git conventions](/documentation/git-conventions.md)
 - [Information architecture heuristics](/documentation/ia-heuristics.md)
 - [Maintainers etiquette](/documentation/maintainers-etiquette.md)
-- [Managing content with Hugo](/documentation/writing-hugo.md)
+- [Managing content with Hugo](/documentation/hugo-content.md)
 - [Proposals](/documentation/proposals/README.md)
 - [Set up pre-commit](/documentation/pre-commit.md)
 - [Using include files](/documentation/include-files.md)