Implement conditional content and other improvements

Author: RebeccaTamachiro

src/content/docs/byoip/service-bindings/cdn-and-spectrum.mdx

@@ -14,22 +14,41 @@ import { Render } from  "~/components";
 
 - You can upgrade individual IPs within a Spectrum prefix to a CDN IP. For example, if you have a Spectrum prefix 203.0.113.0/24, you can upgrade 203.0.113.1 to CDN.
 
+This guide will use the first example, considering a prefix that was onboarded to the CDN and will have a few IPs upgraded to Spectrum.
 
 ## Before you begin
 
-<Render file="service-bindings-prereqs" />
+<Render
+file="service-bindings-prereqs"
+params={{
+	pre_existing_product: "CDN",
+	added_product: "Spectrum"
+}}
+/>
 
 ---
 
 ## Prepare your IPs
 
 ### 1. Get account information
 
-<Render file="service-bindings-account-info" />
+<Render
+file="service-bindings-account-info"
+params={{
+	pre_existing_product: "CDN",
+	added_product: "Spectrum"
+}}
+/>
 
 ### 2. Create service bindings
 
-<Render file="service-bindings-create-binding" />
+<Render
+file="service-bindings-create-binding"
+params={{
+	pre_existing_product: "CDN",
+	added_product: "Spectrum"
+}}
+/>
 
 ### 3. Verify all service bindings
 

src/content/partials/byoip/service-bindings-account-info.mdx

@@ -1,11 +1,13 @@
 ---
-{}
+params:
+ - pre_existing_product
+ - added_product
 ---
 
-import { Example } from "~/components";
+import { Example, APIRequest } from "~/components";
 
-1. Log in to your Cloudflare account and get your [account ID](/fundamentals/setup/find-account-and-zone-ids/) and [API token](/fundamentals/api/get-started/create-token/). The token permissions should include `Account` - `IP Prefixes` - `Edit`.
-2. Make a `GET` request to the [List Services](/api/resources/addressing/subresources/services/methods/list/) endpoint and take note of the `id` associated with the CDN service.
+1. Log in to your Cloudflare account and get your [account ID](/fundamentals/setup/find-account-and-zone-ids/) and [authentication key or token](/fundamentals/api/get-started/). If using an [API token](/fundamentals/api/get-started/create-token/), the permissions should include `Account` - `IP Prefixes` - `Edit`.
+2. Make a `GET` request to the [List Services](/api/resources/addressing/subresources/services/methods/list/) endpoint and take note of the `id` associated with the {props.added_product} service.
 3. Use the [List Prefixes](/api/resources/addressing/subresources/prefixes/methods/list/) endpoint and take note of the `id` associated with the prefix (`cidr`) you will configure.
 
 <Example>
@@ -14,18 +16,18 @@ At this point, continuing the [example](#before-you-begin), you should have a ma
 
 | Variables      | Description                                                                                                                                       |
 | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `{service_id}` | The ID of the CDN service within Cloudflare. <br /><br /> Example: `969xxxxxxxx000xxx0000000x00001bf`                                             |
-| `{prefix_id}`  | The ID of the Magic Transit protected prefix (`203.0.113.0/24`) you want to configure. <br /><br /> Example: `6b25xxxxxxx000xxx0000000x0000cfc` |
+| `{service_id}` | The ID of the {props.added_product} service within Cloudflare. <br /><br /> Example: `969xxxxxxxx000xxx0000000x00001bf`                                             |
+| `{prefix_id}`  | The ID of the {props.pre_existing_product} prefix (`203.0.113.0/24`) you want to configure. <br /><br /> Example: `6b25xxxxxxx000xxx0000000x0000cfc` |
 
 </Example>
 
-4. To confirm you currently have a Magic Transit service binding and that it spans across your entire prefix, make a `GET` request to the [List Service Bindings](/api/resources/addressing/subresources/prefixes/subresources/service_bindings/methods/list/) endpoint. Replace the `{prefix_id}` in the URI path by the actual prefix ID you got from the previous step.
+4. To confirm you currently have a {props.pre_existing_product} service binding and that it spans across your entire prefix, make a `GET` request to the [List Service Bindings](/api/resources/addressing/subresources/prefixes/subresources/service_bindings/methods/list/) endpoint. Replace the `{prefix_id}` in the URI path by the actual prefix ID you got from the previous step.
 
 <Example>
 
-```bash
-curl https://api.cloudflare.com/client/v4/accounts/{account_id}/addressing/prefixes/{prefix_id}/bindings \
---header "Authorization: Bearer <API_TOKEN>"
-```
+<APIRequest
+path="/accounts/{account_id}/addressing/prefixes/{prefix_id}/bindings"
+method="GET"
+/>
 
 </Example>

src/content/partials/byoip/service-bindings-create-binding.mdx

@@ -1,5 +1,7 @@
 ---
-{}
+params:
+ - pre_existing_product
+ - added_product
 ---
 
 import { Example } from "~/components";
@@ -8,13 +10,13 @@ import { Example } from "~/components";
 Once a service binding is created (or deleted), it will take four to six hours to propagate across Cloudflare's global network. Services for the IP addresses in scope will likely be disrupted during this window.
 :::
 
-1. Make a `POST` request to the [Create service binding](/api/resources/addressing/subresources/prefixes/subresources/service_bindings/methods/create/) endpoint, indicating the IP address you want to bind to the CDN. Specify the **corresponding network mask** as needed.
+1. Make a `POST` request to the [Create service binding](/api/resources/addressing/subresources/prefixes/subresources/service_bindings/methods/create/) endpoint, indicating the IP address you want to bind to {props.added_product}. Specify the **corresponding network mask** as needed.
 
 <Example>
 
-Continuing the example, `203.0.113.100/32` designates an IP address that is within the Magic Transit protected prefix `203.0.113.0/24`.
+Continuing the example, `203.0.113.100/32` designates an IP address that is within the {props.pre_existing_product} prefix `203.0.113.0/24`.
 
-Replace the `{prefix_id}` in the URI with your prefix ID from previous steps. Within the request body, the `cidr` value should correspond to the IP address or subnet that you are configuring for use with CDN.
+Replace the `{prefix_id}` in the URI with your prefix ID from previous steps. Within the request body, the `cidr` value should correspond to the IP address or subnet that you are configuring for use with {props.added_product}.
 
 ```bash
 
@@ -36,7 +38,7 @@ In the response body, the initial provisioning state should be `provisioning`.
   "success": true,
   "result": {
     "cidr": "203.0.113.100/32",
-    "id": "<CDN_SERVICE_BINDING_ID>",
+    "id": "<SERVICE_BINDING_ID>",
     "provisioning": {
       "state": "provisioning"
       },

src/content/partials/byoip/service-bindings-prereqs.mdx

@@ -1,5 +1,7 @@
 ---
-{}
+params:
+ - pre_existing_product
+ - added_product
 ---
 
 import { Details } from "~/components";
@@ -8,9 +10,9 @@ Although it is possible to add discrete bindings for non-contiguous CIDR blocks,
 
 <Details header="Example">
 
-**Magic Transit protected prefix:** `203.0.113.0/24`
+**{props.pre_existing_product} protected prefix:** `203.0.113.0/24`
 
-**IPs to upgrade to the CDN:**
+**IPs to upgrade to {props.added_product}:**
 
 `203.0.113.16`<br />
 `203.0.113.17`<br />
@@ -21,12 +23,12 @@ Although it is possible to add discrete bindings for non-contiguous CIDR blocks,
 `203.0.113.22`<br />
 `203.0.113.23`
 
-Add one discrete CDN service binding for `203.0.113.16` with a `/29` netmask.
+Add one discrete {props.added_product} service binding for `203.0.113.16` with a `/29` netmask.
 
 </Details>
 
 Once a service binding is created (or deleted), it will take **four** to **six** hours to propagate across Cloudflare's global network. Services for the IP addresses in scope will likely be disrupted during this window.
 
 :::note
-This guide assumes that the prefix is tied to a single Cloudflare account that has both Magic Transit and CDN properties. If you are using [prefix delegations](/byoip/concepts/prefix-delegations/), the service bindings must be [created](#2-create-service-binding) on the parent account.
+This guide assumes that the prefix is tied to a single Cloudflare account that has both {props.pre_existing_product} and {props.added_product} properties. If you are using [prefix delegations](/byoip/concepts/prefix-delegations/), the service bindings must be [created](#2-create-service-binding) on the parent account.
 :::