DOC-5931 "hierarchy" diagram hook

content/develop/clients/jedis/error-handling.md

@@ -16,20 +16,22 @@ app reliability.
 
 Jedis organizes exceptions in a hierarchy rooted at `JedisException`, which extends `RuntimeException`. All Jedis exceptions are unchecked exceptions:
 
-```
-JedisException
-├── JedisDataException
-│   ├── JedisRedirectionException
-│   │   ├── JedisMovedDataException
-│   │   └── JedisAskDataException
-│   ├── AbortedTransactionException
-│   ├── JedisAccessControlException
-│   └── JedisNoScriptException
-├── JedisClusterException
-│   ├── JedisClusterOperationException
-│   ├── JedisConnectionException
-│   └── JedisValidationException
-└── InvalidURIException
+```hierarchy {type="exception"}
+"JedisException":
+    _meta:
+        description: "Base class for all Jedis exceptions"
+    "JedisDataException":
+        "JedisRedirectionException":
+            "JedisMovedDataException":
+            "JedisAskDataException":
+        "AbortedTransactionException":
+        "JedisAccessControlException":
+        "JedisNoScriptException":
+    "JedisClusterException":
+        "JedisClusterOperationException":
+        "JedisConnectionException":
+        "JedisValidationException":
+    "InvalidURIException":
 ```
 
 ### Key exceptions

content/develop/clients/redis-py/error-handling.md

@@ -17,18 +17,23 @@ app reliability.
 
 ## Exception hierarchy
 
-redis-py organizes exceptions in a hierarchy. The base exception is `redis.RedisError`, with specific subclasses for different error types:
-
-```
-RedisError (base)
-├── ConnectionError
-│   ├── TimeoutError
-│   └── BusyLoadingError
-├── ResponseError
-├── InvalidResponse
-├── DataError
-├── PubSubError
-└── ... (others)
+redis-py organizes exceptions in a hierarchy. The base exception is `redis.RedisError`, with specific subclasses for different error types, as shown below:
+
+```hierarchy {type="exception"}
+"RedisError":
+    _meta:
+        description: "Base class for all redis-py exceptions"
+    "ConnectionError":
+        "TimeoutError":
+        "BusyLoadingError":
+    "ResponseError":
+    "InvalidResponse":
+    "DataError":
+    "PubSubError":
+    "...":
+        _meta:
+            ellipsis: true
+            description: "Other exception types"
 ```
 
 ### Key exceptions

content/integrate/redis-data-integration/data-pipelines/_index.md

@@ -108,10 +108,28 @@ section.
 ###  2. Configure the pipeline
 
 RDI uses a set of [YAML](https://en.wikipedia.org/wiki/YAML)
-files to configure each pipeline. The following diagram shows the folder
-structure of the configuration:
-
-{{< image filename="images/rdi/ingest/ingest-config-folders.webp" width="600px" >}}
+files to configure each pipeline. The folder structure of the
+configuration is shown below:
+
+```hierarchy {type="filesystem"}
+"(root)":
+    "config.yaml":
+        _meta:
+            description: "\"config.yaml\" is the main pipeline configuration file."
+    "jobs":
+        _meta:
+            description: "The 'jobs' folder containing optional job files."
+        "default-job.yaml":
+            _meta:
+                description: "A default job."
+        "job1.yaml":
+          _meta:
+                description: "Each job file must have a unique name."
+        "...":
+            _meta:
+                ellipsis: true
+                description: "Other job files, if required."
+```
 
 The main configuration for the pipeline is in the `config.yaml` file.
 This specifies the connection details for the source database (such

layouts/_default/_markup/render-codeblock-hierarchy.html

@@ -0,0 +1,5 @@
+{{- $type := .Attributes.type | default "generic" -}}
+{{- $noIcons := .Attributes.noicons | default "" -}}
+<pre class="hierarchy-source" data-hierarchy-type="{{ $type }}" data-no-icons="{{ $noIcons }}">{{ .Inner | htmlEscape | safeHTML }}</pre>
+{{ .Page.Store.Set "hasHierarchy" true }}
+

layouts/_default/baseof.html

@@ -99,5 +99,10 @@
     {{ if .Page.Store.Get "hasChecklist" }}
     <script src="{{ "js/checklist.js" | relURL }}"></script>
     {{ end }}
+
+    <!-- Hierarchy functionality -->
+    {{ if .Page.Store.Get "hasHierarchy" }}
+    <script src="{{ "js/hierarchy.js" | relURL }}"></script>
+    {{ end }}
   </body>
 </html>