chore: update academy shortcode usage to match latest theme

Signed-off-by: Aastha <bhat.aasthaa@gmail.com>

Author: AasthathecoderX

content/content-formatting-examples/academy-theme/chapterstyle/_index.md

@@ -9,9 +9,9 @@ draft: true
 The `chapterstyle` shortcode wraps content in a `<div>` with custom inline styles, useful for visually distinguishing chapter or section blocks.
 
 ```text
-{{%/* chapterstyle style="padding: 1rem; border: 1px solid #d0d7de; border-radius: 0.75rem; background: #f8fafc;" */%}}
+{{</* chapterstyle style="padding: 1rem; border: 1px solid #d0d7de; border-radius: 0.75rem; background: #f8fafc;" */>}}
 Your styled content here.
-{{%/* /chapterstyle */%}}
+{{</* /chapterstyle */>}}
 ```
 
 **Parameters:**
@@ -22,6 +22,6 @@ Your styled content here.
 
 **Example:**
 
-{{% chapterstyle style="padding: 1rem; border: 1px solid #d0d7de; border-radius: 0.75rem; background: #f8fafc;" %}}
+{{< chapterstyle style="padding: 1rem; border: 1px solid #d0d7de; border-radius: 0.75rem; background: #f8fafc;" >}}
 This content is wrapped by the `chapterstyle` shortcode. The border, padding, and background color are applied via the `style` parameter. This shortcode is useful for visually grouping related content into a styled container.
-{{% /chapterstyle %}}
+{{< /chapterstyle >}}

content/content-formatting-examples/academy-theme/csvtable-roles/_index.md

@@ -6,10 +6,23 @@ description: Academy theme csvtable-roles shortcode for role-specific permission
 draft: true
 ---
 
-The `csvtable-roles` shortcode reads `static/data/csv/keys-backup.csv` and renders per-role permission tables showing which functions each role has access to.
+The `csvtable-roles` shortcode turns a role permissions matrix into per-role reference tables, so the permissions stay in one CSV instead of hand-maintained markdown that drifts out of sync. It reads every role column and renders a table per role , listing only the permissions that role holds — giving readers a single view of what one role can do.
 
 ```text
-{{</* csvtable-roles */>}}
+{{</* csvtable-roles src="keys-backup.csv" */>}}
 ```
 
-The CSV file must be located at `static/data/csv/keys-backup.csv` with the same format used by `csvtable`.
+**Parameters:**
+
+| Parameter | Description | Default |
+|---|---|---|
+| `src` | Path to the CSV. Resolved against the page bundle first, then `assets/`, then the project root | `static/data/csv/keys-backup.csv` |
+| `headerRow` | 0-based index of the header row. Set to `1` for a CSV with a title row above the header | `0` |
+
+**Example:**
+
+{{< csvtable-roles src="keys-backup.csv" >}}
+
+The CSV needs `Function` and `Feature` columns and one column per role. Every column that isn't `Category`, `Function`, `Feature`, or metadata (`Keychain ID`, `Key ID`, `Inserted`, `Local Provider`) is treated as a role, and a row appears under that role when its cell is `X` or `X*`.
+
+Paths for `assets/` are relative to that directory (`data/keys.csv`), while project-root paths keep their prefix (`static/data/csv/keys-backup.csv`).

content/content-formatting-examples/academy-theme/csvtable/_index.md

@@ -6,10 +6,22 @@ description: Academy theme csvtable shortcode for rendering permissions tables f
 draft: true
 ---
 
-The `csvtable` shortcode reads `static/data/csv/keys-backup.csv` and renders a permissions table grouped by category. Each role column shows a check or cross indicator.
-
+The `csvtable` shortcode turns a role permissions matrix into documentation tables, so the permissions stay in one CSV instead of hand-maintained markdown that drifts out of sync. It groups rows by their `Category` column and renders a table per category, with every role as a column — giving readers a feature-by-feature comparison of role access.
 ```text
-{{</* csvtable */>}}
+{{</* csvtable src="keys-backup.csv" */>}}
 ```
 
-The CSV file must be located at `static/data/csv/keys-backup.csv` and contain columns for Category, Function, Feature, and various role names.
+**Parameters:**
+
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `src` | Path to the CSV. Resolved against the page bundle first, then `assets/`, then the project root | `static/data/csv/keys-backup.csv` |
+| `headerRow` | 0-based index of the header row. Set to `1` for a CSV with a title row above the header | `0` |
+
+**Example:**
+
+{{< csvtable src="keys-backup.csv" >}}
+
+The CSV needs a `Category` column, `Function` and `Feature` columns, and one column per role. `Keychain ID`, `Key ID`, `Inserted`, and `Local Provider` are hidden if present. Role cells render `X` as ✅, `X*` as ✅ *, and anything else as ❌.
+
+Paths for `assets/` are relative to that directory (`data/keys.csv`), while project-root paths keep their prefix (`static/data/csv/keys-backup.csv`).

content/content-formatting-examples/academy-theme/lab-intro/_index.md

@@ -6,18 +6,20 @@ description: Academy theme lab-intro shortcode for storing lab introduction cont
 draft: true
 ---
 
-The `lab-intro` shortcode captures its inner content and stores it on the page scratch pad under the key `lab_intro`. This allows layout templates to retrieve and display lab introduction text in a dedicated section of the page.
+The `lab-intro` shortcode captures its inner content and stores it for output elsewhere on the page , so lab introductions can be authored inline with the rest of the  lab  while rendering in a dedicated section . It emits nothing at the call site — the stored content is rendered by `lab-outro`, which must appear later in the same file.
 
 ```text
-{{%/* lab-intro */%}}
-Welcome to this hands-on lab. In this exercise, you will learn how to deploy a cloud native application using Kubernetes. By the end of this lab, you will be able to create a cluster, deploy workloads, and expose services.
-{{%/* /lab-intro */%}}
+{{</* lab-intro */>}}
+Welcome to this hands-on lab. In this exercise, you will learn how to deploy a cloud-native application using Kubernetes. By the end of this lab, you will be able to create a cluster, deploy workloads, and expose services.
+{{</* /lab-intro */>}}
+
+{{</* lab-outro */>}}
 ```
 
 **Example:**
 
-{{% lab-intro %}}
-Welcome to this hands-on lab. In this exercise, you will learn how to deploy a cloud native application using Kubernetes. By the end of this lab, you will be able to create a cluster, deploy workloads, and expose services.
-{{% /lab-intro %}}
+{{< lab-intro >}}
+Welcome to this hands-on lab. In this exercise, you will learn how to deploy a cloud-native application using Kubernetes. By the end of this lab, you will be able to create a cluster, deploy workloads, and expose services.
+{{< /lab-intro >}} 
 
-The content above is stored in the page's scratch pad. Layout templates can access it via `.Page.Scratch.Get "lab_intro"` to render it in a dedicated area.
+{{< lab-outro >}}

content/content-formatting-examples/academy-theme/lab-outro/_index.md

@@ -0,0 +1,27 @@
+---
+title: Lab Outro
+linkTitle: Lab Outro
+weight: 11
+description: Academy theme lab-outro shortcode for rendering lab introduction content.
+draft: true
+---
+
+The `lab-outro` shortcode renders the content captured earlier by `lab-intro`, marking the point on the page where that content should appear.
+
+```text
+{{</* lab-intro */>}}
+Welcome to this hands-on lab. In this exercise, you will learn how to deploy a cloud-native application using Kubernetes.
+{{</* /lab-intro */>}}
+
+{{</* lab-outro */>}}
+```
+
+**Example:**
+
+{{< lab-intro >}}
+Welcome to this hands-on lab. In this exercise, you will learn how to deploy a cloud-native application using Kubernetes.
+{{< /lab-intro >}}
+
+{{< lab-outro >}}
+
+Shortcodes run in source order, so `lab-outro` must appear after the `lab-intro` it renders. Calling it first logs a build warning and outputs nothing. Only one capture is stored per page, so a second `lab-intro` overwrites the first.

content/content-formatting-examples/academy-theme/svg/_index.md

@@ -2,24 +2,28 @@
 title: SVG
 linkTitle: SVG
 weight: 7
-description: Academy theme svg shortcode for inline SVG icons from assets.
+description: Render an inline SVG icon, resolved from  the page bundle first, then assets.
 draft: true
 ---
 
-The `svg` shortcode renders an inline SVG icon from `assets/icons/{name}.svg`.
+The `svg` shortcode renders an inline SVG icon .
 
 ```text
-{{</* svg name="layer5-academy-icon" */>}}
+{{</* svg name="exoscale-icon" */>}}
+{{</* svg src="1e2a8e46-937c-47ea-ab43-5716e3bcab2e/icons/foo.svg" */>}}
 ```
 
 **Parameters:**
 
 | Parameter | Description | Default |
 |-----------|-------------|---------|
-| `name` | SVG file name (without extension) from `assets/icons/` | _(required)_ |
+| `name` | SVG file name (without extension). Looks for `{name}.svg` in the page bundle, then `assets/icons/{name}.svg` | _(required, unless `src` is set)_ |
+| `src` | Explicit path including the extension, resolved against the page bundle, then `assets/`. Takes precedence over `name` | _(none)_ |
 
 **Example:**
 
-<!-- The icon renders inline: {{< svg name="exoscale-icon" >}} -->
+ The icon renders inline: {{< svg name="exoscale-icon" >}} 
 
-To add your own SVG icons, place `.svg` files in the `assets/icons/` directory.
+To add your own SVG icons, place `.svg` files in the `assets/icons/` directory, or alongside `index.md` in a page bundle to keep them with the page that uses them.
+
+Use `src` when the file lives outside `assets/icons/` — for example an org-scoped directory like `assets/{org-id}/icons/`. When resolved from `assets/`, paths are relative to `assets/`, so leave that prefix off: a file at `assets/1e2a8e46-937c-47ea-ab43-5716e3bcab2e/icons/foo.svg` is referenced as `src="1e2a8e46-937c-47ea-ab43-5716e3bcab2e/icons/foo.svg"`. When resolved from the page bundle, `src` is relative to the page bundle itself. A build warning is logged if the file is found in neither location.

content/content-formatting-examples/academy-theme/swaggerui-api/_index.md

@@ -0,0 +1,27 @@
+---
+title: SwaggerUI API
+linkTitle: SwaggerUI API
+weight: 11
+description: Render the Academy Theme swaggerui-api shortcode.
+draft: true
+---
+
+The `swaggerui-api` shortcode renders an interactive Swagger UI viewer for an OpenAPI spec.
+
+```text
+{{</* swaggerui-api src="example.json" */>}}
+{{</* swaggerui-api src="/data/openapi.json" */>}}
+```
+
+**Parameters:**
+
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `src` | Path to the OpenAPI spec. Root-relative paths (files under `static/`) are used as-is; anything else resolves against the page bundle, then `assets/` | _(required)_ |
+| `deepLinking` | `"true"` writes the expanded operation into the URL fragment. Only safe with one viewer per page | `"false"` |
+
+**Example:**
+
+{{< swaggerui-api src="example.json" >}}
+
+Place the spec alongside `index.md` in a page bundle to keep it with the page that uses it, or in `assets/` to share it across pages. The spec must be part of this site — remote URLs are rejected at build time.

content/content-formatting-examples/academy-theme/swaggerui-api/example.json

@@ -0,0 +1,69 @@
+{
+  "openapi": "3.0.0",
+  "info": {
+    "title": "Example Academy API",
+    "version": "1.0.0",
+    "description": "A sample API specification for demonstrating the Redoc and SwaggerUI shortcodes."
+  },
+  "paths": {
+    "/api/courses": {
+      "get": {
+        "summary": "List courses",
+        "description": "Returns a list of all available courses.",
+        "responses": {
+          "200": {
+            "description": "A list of courses.",
+            "content": {
+              "application/json": {
+                "schema": {
+                  "type": "array",
+                  "items": {
+                    "$ref": "#/components/schemas/Course"
+                  }
+                }
+              }
+            }
+          }
+        }
+      }
+    },
+    "/api/courses/{id}": {
+      "get": {
+        "summary": "Get a course",
+        "description": "Returns a single course by ID.",
+        "parameters": [
+          {
+            "name": "id",
+            "in": "path",
+            "required": true,
+            "schema": { "type": "string" }
+          }
+        ],
+        "responses": {
+          "200": {
+            "description": "A course object.",
+            "content": {
+              "application/json": {
+                "schema": { "$ref": "#/components/schemas/Course" }
+              }
+            }
+          },
+          "404": { "description": "Course not found." }
+        }
+      }
+    }
+  },
+  "components": {
+    "schemas": {
+      "Course": {
+        "type": "object",
+        "properties": {
+          "id": { "type": "string", "example": "cloud-101" },
+          "title": { "type": "string", "example": "Cloud Fundamentals" },
+          "description": { "type": "string", "example": "An introduction to cloud computing concepts." },
+          "duration": { "type": "string", "example": "2 hours" }
+        }
+      }
+    }
+  }
+}