Chore: Merge branch 'main' into add/coveo-error-msg

Author: lamATnginx

.github/renovate.json

@@ -8,6 +8,7 @@
     ":configMigration",
     "abandonments:recommended"
   ],
+  "commitMessagePrefix": "Chore:",
   "commitMessageLowerCase": "never",
   "labels": ["dependency"]
 }

.github/workflows/nginx-documentation-build.yml

@@ -12,7 +12,7 @@ jobs:
 
     steps:
       - name: Checkout hugo theme
-        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.7.1
+        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
         with:
           fetch-depth: 0 # This is required for hugo Lastmod to function properly
 

exampleSite/content/test-product/call-out/all-callouts.md

@@ -17,10 +17,6 @@ This is a plain callout with no title. It has a [link](#plain-callouts) to a hea
 This is a plain callout with a title. It has a [link](#plain-callouts) to a heading on this page. Its shortcode is `<call-out>` with a custom title parameter.
 {{</call-out>}}
 
-{{<before-you-begin>}}
-This is a plain callout with a default title for its type. It has a [link](#plain-callouts) to a heading on this page. Its shortcode is `<before-you-begin>`.
-{{</before-you-begin>}}
-
 ## Side Callouts
 
 Naturally, callouts should contain less text within them than the text it lives next to. We do this for several reasons. Firstly, it looks weird to have a big empty space in the primary content area. Secondly, if you have more text in the callout, then it stops being a callout. I have asked an LLM to lengthen this passage.
@@ -71,24 +67,3 @@ And a final line.
 This is a Warning callout with a custom title. There was previously a bug with **bold text** that we should be aware of and continue to check for. This callout was invoked with the `<call-out>` shortcode with the `.warning` class, and a custom title.
 {{</call-out>}}
 
-
-
-
-## Old "plain" callouts
-The following will not have special styling, but are pre-existing shortcodes.
-
-{{<note>}}
-This is `<note>`. In oldframe it should have `note:` in bold, at the start.
-{{</note>}}
-
-{{<tip>}}
-This is `<tip>`. In oldframe it should have `tip:` in bold, at the start.
-{{</tip>}}
-
-{{<before-you-begin>}}
-This is `<before-you-begin>`.
-{{</before-you-begin>}}
-
-{{<see-also>}}
-This is `<see-also>`.
-{{</see-also>}}

exampleSite/content/test-product/call-out/call-out-code-lists.md

@@ -10,26 +10,26 @@ weight: 200
 
 - **Using an instance's configuration for the group configuration**: If an instance is the first to join a config sync group and the group's configuration hasn't been defined, the instance’s configuration will become the group’s configuration. Any instances added later will automatically inherit this configuration. 
 
-  {{< note >}} If you add multiple instances to a single config sync group, simultaneously (with automation), follow these steps. Your instances will inherit your desired configuration:
+  {{< call-out "note" >}} If you add multiple instances to a single config sync group, simultaneously (with automation), follow these steps. Your instances will inherit your desired configuration:
 
   1. Create a config sync group.
   1. Add a configuration to the config sync group, so all instances inherit it.
   1. Add the instances in a separate operation.
 
-  Your instances should synchronize with your desired configuration within 30 seconds. {{< /note >}}
+  Your instances should synchronize with your desired configuration within 30 seconds. {{< /call-out >}}
 
 
 ## Text with Unordered List in note
 
 - **Using an instance's configuration for the group configuration**: If an instance is the first to join a config sync group and the group's configuration hasn't been defined, the instance’s configuration will become the group’s configuration. Any instances added later will automatically inherit this configuration. 
 
-  {{< note >}} If you add multiple instances to a single config sync group, simultaneously (with automation), follow these steps. Your instances will inherit your desired configuration:
+  {{< call-out "note" >}} If you add multiple instances to a single config sync group, simultaneously (with automation), follow these steps. Your instances will inherit your desired configuration:
 
   - Create a config sync group.
   - Add a configuration to the config sync group, so all instances inherit it.
   - Add the instances in a separate operation.
 
-  Your instances should synchronize with your desired configuration within 30 seconds. {{< /note >}}
+  Your instances should synchronize with your desired configuration within 30 seconds. {{< /call-out >}}
 
 
 ## Callout within list

exampleSite/content/test-product/everything.md

@@ -4,12 +4,6 @@ title: Everything
 weight: 200
 ---
 
-## before-you-begin
-
-{{< before-you-begin >}}
-Before you can set users' passwords, ensure you have [created users](#create-users) in NGINX Instance Manager. Once you've created the users, you can use one of the following options to set their passwords.
-{{< /before-you-begin >}}
-
 ## bootstrap-table
 
 {{<bootstrap-table "table">}}
@@ -60,10 +54,6 @@ This won't render anything.
 
 {{< include "nginx-openid-repo-note.txt" >}}
 
-## see-also
-
-{{< see-also >}}See also!{{< /see-also >}}
-
 
 ## details
 <details>
@@ -75,11 +65,11 @@ And this is the content on how to do so.
 <details open>
     <summary>example dynamic-agent.conf</summary>
 
-{{<note>}}
+{{<call-out "note">}}
 Default location in Linux environments: `/var/lib/nginx-agent/agent-dynamic.conf`
 
 Default location in FreeBSD environments: `/var/db/nginx-agent/agent-dynamic.conf`
-{{</note>}}
+{{</call-out>}}
 
 ```yaml
 # Dynamic configuration file for NGINX Agent.

layouts/partials/callout.html

@@ -36,7 +36,7 @@
   <div>
     <div class="call-out-type">
       {{ partial "lucide" (dict "context" . "icon" $icon) . }}
-      {{ $title }}
+      {{ if $title }}{{ $title }}{{ else }}{{ $type }}{{end}}
     </div>
     <div class="callout-content">
       {{- .content | markdownify -}}