DOC-6026 added embed to RDI Cloud page

Author: andy-stark-redis

content/embeds/rdi-when-to-use.md

@@ -16,8 +16,8 @@ RDI is a good fit when:
   [CDC]({{< relref "/integrate/redis-data-integration/data-pipelines#pipeline-lifecycle" >}})
   would not exceed 10K records per second.
 - You don’t need to perform join operations on the data from several tables
-  into a nested Redis JSON object.
-- RDI supports the data transformations you need for your app.
+  into a [nested Redis JSON object]({{< relref "/integrate/redis-data-integration/data-pipelines/data-denormalization#joining-one-to-many-relationships" >}}).
+- RDI supports the [data transformations]({{< relref "/integrate/redis-data-integration/data-pipelines/transform-examples" >}}) you need for your app.
 - Your data caching needs are too complex or demanding to implement and maintain yourself.
 - Your database administrator has reviewed RDI's requirements for the source database and
   confirmed that they are acceptable.

content/operate/rc/databases/rdi/_index.md

@@ -23,6 +23,20 @@ RDI helps Redis customers sync Redis Cloud with live data from their primary dat
 
 Using RDI with Redis Cloud simplifies managing your data integration pipeline. No need to worry about hardware or underlying infrastructure, as Redis Cloud manages that for you. Creating the data flow from source to target is much easier, and there are validations in place to reduce errors.
 
+## Is RDI a good fit for my architecture?
+
+RDI is designed to support apps that must use a disk-based database as the system of record
+but must also be fast and scalable. This is a common requirement for mobile and web
+apps with a rapidly-growing number of users; the performance of the main database is fine at first
+but it will soon struggle to handle the increasing demand without a cache.
+
+Use the information in the sections below to determine whether RDI is a good fit for your architecture.
+
+```decision-tree
+```
+
+{{< embed-md "rdi-when-to-use.md" >}}
+
 ## Data pipeline architecture
 
 An RDI data pipeline sits between your source database and your target Redis database. Initially, the pipeline reads all of the data and imports it into the target database during the *initial sync* phase. After this initial sync is complete, the data pipeline enters the *streaming* phase, where changes are captured as they happen. Changes in the source database are added to the target within a few seconds of capture. The data pipeline translates relational database rows to Redis hashes or JSON documents. 

layouts/_default/_markup/render-codeblock-decision-tree.html

@@ -1,31 +1,38 @@
 {{- /* Render hook for decision tree code blocks */ -}}
-{{- /* Preserve YAML source for visual display and JavaScript parsing */ -}}
-<pre class="decision-tree-source">{{ .Inner | htmlEscape | safeHTML }}</pre>
+{{- /* Check if content is empty (used to trigger JS loading without rendering) */ -}}
+{{- $trimmedContent := strings.TrimSpace .Inner -}}
+{{- if eq $trimmedContent "" -}}
+  {{- /* Empty code block - just set the flag to load the JS, don't render anything */ -}}
+  {{ .Page.Store.Set "hasDecisionTree" true }}
+{{- else -}}
+  {{- /* Preserve YAML source for visual display and JavaScript parsing */ -}}
+  <pre class="decision-tree-source">{{ .Inner | htmlEscape | safeHTML }}</pre>
 
-{{- /* Extract id and scope from YAML for metadata (only top-level fields) */ -}}
-{{- $lines := split .Inner "\n" -}}
-{{- $id := "" -}}
-{{- $scope := "" -}}
-{{- range $lines -}}
-  {{- /* Only process lines that don't start with whitespace (top-level fields) */ -}}
-  {{- if and (gt (len .) 0) (ne (index . 0) 32) (ne (index . 0) 9) -}}
-    {{- $trimmed := strings.TrimSpace . -}}
-    {{- if strings.HasPrefix $trimmed "id:" -}}
-      {{- $afterPrefix := strings.Replace $trimmed "id:" "" 1 -}}
-      {{- $id = strings.TrimSpace $afterPrefix -}}
-    {{- end -}}
-    {{- if strings.HasPrefix $trimmed "scope:" -}}
-      {{- $afterPrefix := strings.Replace $trimmed "scope:" "" 1 -}}
-      {{- $scope = strings.TrimSpace $afterPrefix -}}
+  {{- /* Extract id and scope from YAML for metadata (only top-level fields) */ -}}
+  {{- $lines := split .Inner "\n" -}}
+  {{- $id := "" -}}
+  {{- $scope := "" -}}
+  {{- range $lines -}}
+    {{- /* Only process lines that don't start with whitespace (top-level fields) */ -}}
+    {{- if and (gt (len .) 0) (ne (index . 0) 32) (ne (index . 0) 9) -}}
+      {{- $trimmed := strings.TrimSpace . -}}
+      {{- if strings.HasPrefix $trimmed "id:" -}}
+        {{- $afterPrefix := strings.Replace $trimmed "id:" "" 1 -}}
+        {{- $id = strings.TrimSpace $afterPrefix -}}
+      {{- end -}}
+      {{- if strings.HasPrefix $trimmed "scope:" -}}
+        {{- $afterPrefix := strings.Replace $trimmed "scope:" "" 1 -}}
+        {{- $scope = strings.TrimSpace $afterPrefix -}}
+      {{- end -}}
     {{- end -}}
   {{- end -}}
-{{- end -}}
 
-{{- /* Embed metadata as custom JSON for AI agents */ -}}
-{{- $metadata := dict "type" "decision-tree" "id" $id "scope" $scope -}}
+  {{- /* Embed metadata as custom JSON for AI agents */ -}}
+  {{- $metadata := dict "type" "decision-tree" "id" $id "scope" $scope -}}
 
-{{ $jsonMetadata := $metadata | jsonify (dict "indent" "  ") }}
-{{ printf "<script type=\"application/json\" data-redis-metadata=\"decision-tree\">\n%s\n</script>" $jsonMetadata | safeHTML }}
+  {{ $jsonMetadata := $metadata | jsonify (dict "indent" "  ") }}
+  {{ printf "<script type=\"application/json\" data-redis-metadata=\"decision-tree\">\n%s\n</script>" $jsonMetadata | safeHTML }}
 
-{{ .Page.Store.Set "hasDecisionTree" true }}
+  {{ .Page.Store.Set "hasDecisionTree" true }}
+{{- end -}}