Merge branch 'main' into dos-release-4.6

Author: ADubhlaoich

.github/ISSUE_TEMPLATE/feature_request.md renamed to .github/ISSUE_TEMPLATE/1-feature_request.md

@@ -0,0 +1,24 @@
+---
+name: Story task
+about: This template is for a story or task, encompassing a single work item for completion
+title: ""
+labels: "documentation"
+projects: ["nginxinc/32"]
+assignees: ""
+---
+
+*Remove italicized directions as relevant to reduce noise in the issue description.*
+
+## Overview
+
+*Written as a user story*.
+
+**As a** <user>, **I want** <thing>, **So I can** <action>.
+
+## Description
+
+*Add the finer details of what this task involves and is trying to accomplish. A problem well defined is half-solved*.
+
+## Acceptance criteria
+
+*Add any exacting acceptance criteria for the task to be complete. Start with known hard requirements, since they may create blockers.*

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

@@ -0,0 +1,40 @@
+---
+name: Epic overview
+about: This template is for planning an epic, which is a large body of effort involving multiple stories or tasks
+title: ""
+labels: "epic, documentation"
+projects: ["nginxinc/32"]
+assignees: ""
+---
+
+*Remove italicized directions as relevant to reduce noise in the issue description.*
+
+## Description
+
+*Write a high-level description of what the body of work for this epic includes.*
+
+## Goals
+
+*Describe the intent of the epic and what the intended impact is for this effort.*
+
+## User stories
+
+*Add a user story for relevant persona to this epic, who are the stakeholders*.
+
+**As a** <user>,
+**I want** <thing>,
+**So I can** <action>.
+
+**As a** <user>,
+**I want** <thing>,
+**So I can** <action>.
+
+## Tasks
+
+*Create a simple list of tasks necessary for this epic. Finer details should be kept to sub-issues/tasks/stories.*
+
+- Example task 1
+- Example task 1
+- Example task 1
+- Example task 1
+- Example task 1

.github/ISSUE_TEMPLATE/3-story_task.md

@@ -0,0 +1,44 @@
+---
+name: Content release plan
+about: This template is for a content release plan, typically tied to a product release
+title: " v#.# content release plan"
+labels: "documentation"
+projects: ["nginxinc/32"]
+assignees: ""
+---
+
+*Remove italicized directions as relevant to reduce noise in the issue description.*
+
+## Overview
+
+- **Product name**: 
+- **Release date**: 
+
+A content release plan establishes and tracks the documentation work for a product related to a release. 
+
+Add tickets to this content release plan as sub-issues, and update it as you go along.
+
+## Description
+
+*Write a high-level summary of changes expected in this release*.
+
+## User stories
+
+**As a** technical writer, 
+**I want** a content release plan for my product, 
+**So I can** ensure correct content is released alongside the latest version of the product. 
+
+**As a** product owner, 
+**I want** a content release plan for my product, 
+**So I can** ensure the product team includes documentation as part of changes to the product. 
+
+## Tasks
+
+*Create a simple list of tasks necessary for this content plan. Finer details can be kept to sub-issues.*
+*Each task item should have a 1:1 relationship with a documentation item, which could be an engineering issue.*
+
+- [ ] Update changelog/release notes
+- [ ] Update version reference information (Such as technical specifications, version shortcodes)
+- [ ] Update any other documentation impacted by changes in this release
+- Additional task 1
+- Additional task 2

.github/ISSUE_TEMPLATE/4-epic_overview.md

@@ -16,14 +16,13 @@ If you're an employee of F5/NGINX, also read [For F5/NGINX Employees](./F5-NGINX
 You will need to install Hugo _or_ Docker to build and preview docs in your local development environment.
 Refer to the [Hugo installation instructions](https://gohugo.io/getting-started/installing/) for more information.
 
-**NOTE**: We are currently running [Hugo v0.134.2](https://github.com/gohugoio/hugo/releases/tag/v0.134.2) in production.
-
 
 Although not a strict requirement, markdown-link-check is also used in documentation development.
 
 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.
 
 - [Installing Hugo](https://gohugo.io/getting-started/installing/)
+  - **NOTE**: We are currently running [Hugo v0.134.2](https://github.com/gohugoio/hugo/releases/tag/v0.134.2) in production.
 - [Installing markdownlint-cli](https://github.com/igorshubovych/markdownlint-cli?tab=readme-ov-file#installation)
 - [Installing markdown-link-check](https://github.com/tcort/markdown-link-check?tab=readme-ov-file#installation).
 
@@ -35,7 +34,11 @@ The configuration files are as follows:
 
 ## Local Docs Development
 
-To build the documentation locally, use the `make` command in the documentation folder with these targets:
+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:
+
+`make hugo-update`
+
+Once you've updated the theme, you can use these targets:
 
 ```text
 make watch        - Runs a local Hugo server, allowing for changes to be previewed in a  browser.
@@ -133,12 +136,14 @@ Supported callouts:
 - `caution`
 - `warning`
 
-You can also create custom callouts using the `call-out` shortcode `{{< call-out "type" "header" "font-awesome icon >}}`. For example:
+You can also create custom callouts using the `call-out` shortcode `{{< call-out "type position" "header" "font-awesome icon >}}`. For example:
 
 ```md
-{{<call-out "important" "JWT file required for upgrade" "fa fa-exclamation-triangle">}}
+{{<call-out "important side-callout" "JWT file required for upgrade" "fa fa-exclamation-triangle">}}
 ```
 
+By default, all custom callouts are included inline, unless you add `side-callout` which places the callout to the right of the content.
+
 Here are some other shortcodes:
 
 - `fa`: Inserts a Font Awesome icon

.github/ISSUE_TEMPLATE/5-content_plan.md

@@ -1,9 +1,8 @@
 ---
-title: "NGINX Agent"
-description: "NGINX Agent is a companion daemon for your NGINX Open Source or NGINX Plus instance."
-linkTitle: "NGINX Agent"
-menu: docs
+title: NGINX Agent
+description: NGINX Agent is a companion daemon for your NGINX Open Source or NGINX
+  Plus instance.
 url: /nginx-agent/
 cascade:
-  logo: "NGINX-product-icon.png"
----
+  logo: NGINX-product-icon.png
+---

CONTRIBUTING_DOCS.md

@@ -1,8 +1,6 @@
 ---
-title: "Configuration"
-description: "Learn how to configure NGINX Agent."
-linkTitle: "Configuration"
-weight: "400"
-menu: docs
+title: Configuration
+description: Learn how to configure NGINX Agent.
+weight: 400
 url: /nginx-agent/configuration/
----
+---

content/agent/_index.md

@@ -1,12 +1,11 @@
 ---
-title: "Basic configuration"
+title: Basic configuration
 draft: false
 weight: 100
 toc: true
-tags: [ "docs" ]
-docs: "DOCS-1229"
-categories: ["configuration"]
-doctypes: ["task"]
+docs: DOCS-1229
+type:
+- how-to
 ---
 
 The following sections explain how to configure NGINX Agent using configuration files, CLI flags, and environment variables.

content/agent/configuration/_index.md

@@ -1,11 +1,10 @@
 ---
-title: "Features configuration"
+title: Features configuration
 draft: false
 weight: 150
 toc: true
-tags: [ "docs" ]
-categories: ["configuration"]
-doctypes: ["task"]
+type:
+- how-to
 ---
 
 ## Overview