[Magic] Refactor Magic partials

src/content/changelog/magic-cloud-networking/2024-12-05-cloud-onramp-terraform.mdx

@@ -10,6 +10,6 @@ You can now generate customized terraform files for building cloud network on-ra
 
 [Magic Cloud](/magic-cloud-networking/) can scan and discover existing network resources and generate the required terraform files to automate cloud resource deployment using their existing infrastructure-as-code workflows for cloud automation.
 
-<Render file="terraform-setup-scenarios" product="magic-cloud-networking" />
+<Render file="terraform-setup-scenarios" product="networking-services" />
 
 For more details, refer to [Set up with Terraform](/magic-cloud-networking/cloud-on-ramps/#set-up-with-terraform).

src/content/changelog/network-interconnect/2024-12-17-bgp-support-cni.mdx

@@ -9,4 +9,4 @@ products:
 
 import { Render } from "~/components";
 
-<Render file="bgp-peering-overview" product="network-interconnect" />
+<Render file="routing/bgp-peering-overview" product="networking-services" />

src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-bandwidth-analytics.mdx

@@ -6,4 +6,6 @@ title: Querying Magic Transit and Magic WAN tunnel bandwidth analytics with Grap
 
 import { Render } from "~/components"
 
-<Render file="graphql/query-magic-transit-bandwidth-graphql" product="magic-transit" params={{ productName: "Magic Transit or Magic WAN" }} />
+<Render file="graphql/query-magic-transit-bandwidth-graphql"
+	product="networking-services"
+	params={{ productName: "Magic Transit or Magic WAN" }} />

src/content/docs/analytics/graphql-api/tutorials/querying-magic-transit-tunnel-healthcheck-results.mdx

@@ -6,4 +6,7 @@ title: Querying Magic Transit and Magic WAN tunnel health check results with Gra
 
 import { Render } from "~/components"
 
-<Render file="graphql/query-magic-transit-health-checks" product="magic-transit" params={{ productName: "Magic Transit or Magic WAN" }} />
+<Render file="graphql/query-magic-transit-health-checks"
+	product="networking-services"
+	params={{ productName: "Magic Transit or Magic WAN" }}
+/>

src/content/docs/magic-cloud-networking/cloud-on-ramps.mdx

@@ -8,4 +8,7 @@ sidebar:
 
 import { Render } from "~/components"
 
-<Render file="magic-wan-on-ramps" params={{ mwanAccount: "Have a Magic WAN account. Contact your account team to learn more." }} />
+<Render file="routing/mcn-magic-wan-on-ramps"
+	product="networking-services"
+	params={{ mwanAccount: "Have a Magic WAN account. Contact your account team to learn more." }}
+/>

src/content/docs/magic-firewall/how-to/enable-magic-roles.mdx

@@ -8,4 +8,4 @@ sidebar:
 
 import { Render } from "~/components"
 
-<Render file="magic-user-role" product="magic-transit" />
+<Render file="magic-user-role" product="networking-services" />

src/content/docs/magic-network-monitoring/magic-transit-integration.mdx

@@ -8,4 +8,4 @@ sidebar:
 
 import { Render } from "~/components"
 
-<Render file="magic-transit-integration" />
+<Render file="mnm-magic-transit-integration" product="networking-services" />

src/content/docs/magic-transit/analytics/index.mdx

@@ -12,7 +12,7 @@ description: Use Magic Transit's different analytic options for an overview of
 import { Render } from "~/components";
 
 <Render file="analytics/overview"
-	product="magic-wan"
+	product="networking-services"
 	params={{
 		productName: "Magic Transit",
 		analyticsAnchorHeading: "#magic-transit-network-analytics",

src/content/docs/magic-transit/analytics/network-analytics.mdx

@@ -22,4 +22,4 @@ Source/destination tunnel data in Network Analytics includes:
 
 ## Access Magic Tunnel analytics
 
-<Render file="analytics/network-analytics" product="magic-wan" />
+<Render file="analytics/network-analytics" product="networking-services" />

src/content/docs/magic-transit/analytics/query-bandwidth.mdx

@@ -8,4 +8,7 @@ sidebar:
 
 import { Render } from "~/components"
 
-<Render file="graphql/query-magic-transit-bandwidth-graphql" params={{ productName: "Magic Transit" }} />
+<Render file="graphql/query-magic-transit-bandwidth-graphql"
+	product="networking-services"
+	params={{ productName: "Magic Transit" }}
+/>

src/content/docs/magic-transit/analytics/query-tunnel-health.mdx

@@ -8,4 +8,6 @@ sidebar:
 
 import { Render } from "~/components"
 
-<Render file="graphql/query-magic-transit-health-checks" params={{ productName: "Magic Transit" }} />
+<Render file="graphql/query-magic-transit-health-checks"
+	product="networking-services"
+	params={{ productName: "Magic Transit" }} />

src/content/docs/magic-transit/analytics/traceroutes.mdx

@@ -9,6 +9,6 @@ import { Render } from "~/components";
 
 <Render
 	file="analytics/traceroutes"
-	product="magic-wan"
+	product="networking-services"
 	params={{ productName: "Transit" }}
 />

src/content/docs/magic-transit/get-started.mdx

@@ -59,18 +59,19 @@ To check your prefixes, you can use [Cloudflare's RPKI Portal](https://rpki.clou
 
 <Render
 	file="prerequisites/maximum-segment-size"
+	product="networking-services"
 	params={{ productName: "Magic Transit" }}
 />
 
 #### MSS clamping recommendations
 
 ##### GRE tunnels as off-ramp
 
-<Render file="mtu-mss/mss-clamping-gre" />
+<Render file="magic-transit/mtu-mss/mss-clamping-gre" product="networking-services" />
 
 ##### IPsec tunnels
 
-<Render file="mtu-mss/mss-clamping-ipsec" />
+<Render file="magic-transit/mtu-mss/mss-clamping-ipsec" product="networking-services" />
 
 :::caution[Important]
 Refer to your device documentation to check if it sets IPsec MSS clamping automatically. If that is not the case and you are using IPsec inside GRE, you have to set MSS clamp manually.
@@ -88,7 +89,9 @@ Refer to [Maximum transmission unit and maximum segment size](/magic-transit/ref
 
 ### Follow router vendor guidelines
 
-<Render file="prerequisites/router-vendor-guidelines-mss-settings-origin" />
+<Render file="prerequisites/router-vendor-guidelines-mss-settings-origin"
+	product="networking-services"
+/>
 
 ## 3. Configure tunnels
 

src/content/docs/magic-transit/how-to/bgp-peering.mdx

@@ -8,8 +8,8 @@ sidebar:
 import { Render } from "~/components"
 
 <Render
-	file="bgp-peering"
-	product="network-interconnect"
+	file="routing/bgp-peering"
+	product="networking-services"
 	params={{
 		productName: "Magic Transit",
 		productPath: "/magic-transit/reference/tunnel-health-checks/",

src/content/docs/magic-transit/how-to/check-tunnel-health-dashboard.mdx

@@ -6,8 +6,8 @@ title: Check tunnel health in the dashboard
 import { Render } from "~/components";
 
 <Render
-	file="tunnel-healthchecks-dash"
-	product="magic-wan"
+	file="tunnel-health/check-tunnel-healthchecks-dash"
+	product="networking-services"
 	params={{
 		dashInfo:
 			"The dashboard shows the global view of tunnel health as measured from all Cloudflare locations.",

src/content/docs/magic-transit/how-to/configure-magic-tunnel-alerts.mdx

@@ -8,8 +8,8 @@ description: Use the API to set up and configure Magic Tunnel health alerts
 import { Render } from "~/components";
 
 <Render
-	file="magic-tunnel-health-alerts/magic-tunnel-health-alerts"
-	product="magic-wan"
+	file="tunnel-health/magic-tunnel-health-alerts"
+	product="networking-services"
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",

src/content/docs/magic-transit/how-to/configure-static-routes.mdx

@@ -13,7 +13,8 @@ description: Magic Transit uses a static configuration to route your traffic
 import { Render } from "~/components"
 
 <Render
-	file="static-routes"
+	file="routing/static-routes"
+	product="networking-services"
 	params={{
 		magicProduct: "Magic Transit",
 		productName: "Magic Transit",

src/content/docs/magic-transit/how-to/configure-tunnels.mdx

@@ -11,7 +11,8 @@ description: Cloudflare recommends two tunnels for each ISP and network location
 
 import { GlossaryTooltip, Render } from "~/components";
 
-<Render file="configure-tunnels"
+<Render file="routing/configure-tunnels"
+	product="networking-services"
 	params={{
 		magicWord: "Magic Transit",
 		productName: "Magic Transit",

src/content/docs/magic-transit/how-to/enable-magic-roles.mdx

@@ -9,4 +9,4 @@ description: You can determine which users have, or do not have, configuration
 
 import { Render } from "~/components"
 
-<Render file="magic-user-role" />
+<Render file="magic-user-role" product="networking-services" />

src/content/docs/magic-transit/how-to/tunnel-health-checks.mdx

@@ -7,6 +7,7 @@ import { Render } from "~/components";
 
 <Render
 	file="tunnel-health/update-tunnel-health-checks-frequency"
+	product="networking-services"
 	params={{
 		productName: "Magic Transit.",
 		healthChecksUrl: "/magic-transit/reference/tunnel-health-checks/",

src/content/docs/magic-transit/magic-network-monitoring.mdx

@@ -8,4 +8,4 @@ sidebar:
 
 import { Render } from "~/components"
 
-<Render file="magic-transit-integration" product="magic-network-monitoring" />
+<Render file="mnm-magic-transit-integration" product="networking-services" />

src/content/docs/magic-transit/network-interconnect.mdx

@@ -12,7 +12,7 @@ import { Render } from "~/components";
 
 <Render
   file="magic-cni"
-  product="network-interconnect"
+  product="networking-services"
   params={{
     magic: "Magic Transit",
     productName: "Magic Transit",

src/content/docs/magic-transit/reference/anti-replay-protection.mdx

@@ -9,8 +9,8 @@ description: If you use Magic Transit and anycast IPsec tunnels, you will need
 import { Render } from "~/components";
 
 <Render
-	file="anti-replay-protection"
-	product="magic-wan"
+	file="reference/anti-replay-protection"
+	product="networking-services"
 	params={{
 		productName: "Magic Transit",
 		productPath: "/magic-transit/how-to/configure-tunnels/#add-tunnels",

src/content/docs/magic-transit/reference/magic-tunnels.mdx

@@ -6,4 +6,7 @@ title: Magic Tunnels background information
 
 import { Render } from "~/components"
 
-<Render file="magic-tunnel-health-alerts/magic-tunnels-slos" product="magic-wan" params={{ tunnelStatePath: "/magic-transit/reference/tunnel-health-checks/#tunnel-state-determination"	}} />
+<Render file="reference/magic-tunnels-slos"
+	product="networking-services"
+	params={{ tunnelStatePath: "/magic-transit/reference/tunnel-health-checks/#tunnel-state-determination"	}}
+/>

src/content/docs/magic-transit/reference/mtu-mss.mdx

@@ -8,7 +8,8 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="mtu-mss/mtu-mss"
+	file="reference/mtu-mss"
+	product="networking-services"
 	params={{
 		magicProduct: "Magic Transit",
 		productName: "Magic Transit"

src/content/docs/magic-transit/reference/traffic-steering.mdx

@@ -11,7 +11,8 @@ description: Magic Transit uses a static configuration to route traffic through
 import { Render } from "~/components";
 
 <Render
-	file="traffic-steering"
+	file="reference/traffic-steering"
+	product="networking-services"
 	params={{
 		productName: "Magic Transit",
 		greURL: "/magic-transit/reference/tunnels/",

src/content/docs/magic-transit/reference/tunnel-health-checks.mdx

@@ -9,7 +9,8 @@ description: Magic Transit uses probes to check for tunnel health. Review
 import { Render } from "~/components";
 
 <Render
-	file="tunnel-health/tunnel-health-checks"
+	file="reference/tunnel-health-checks"
+	product="networking-services"
 	params={{
 		addTunnels: "/magic-transit/how-to/configure-tunnels/#add-tunnels",
 		changeHealthCheckRate: "/magic-transit/how-to/tunnel-health-checks/",

src/content/docs/magic-transit/reference/tunnels.mdx

@@ -10,7 +10,8 @@ description: Magic Transit uses Generic Routing Encapsulation (GRE) and IPsec
 import { Render } from "~/components";
 
 <Render
-	file="tunnels-reference/tunnels-encapsulation"
+	file="reference/tunnels-encapsulation"
+	product="networking-services"
 	params={{
 		productName: "Magic Transit",
 		mssURL: "/magic-transit/get-started/#set-maximum-segment-size",

src/content/docs/magic-wan/analytics/index.mdx

@@ -12,6 +12,7 @@ description: Use Magic WAN's different analytic options for an overview of the
 import { Render } from "~/components";
 
 <Render file="analytics/overview"
+	product="networking-services"
 	params={{
 		magicProduct: "Magic WAN",
 		productName: "Magic WAN",

src/content/docs/magic-wan/analytics/network-analytics.mdx

@@ -37,4 +37,4 @@ Customers can filter the data in Network Analytics on different packet character
 
 ## Magic Tunnel traffic analytics
 
-<Render file="analytics/network-analytics" />
+<Render file="analytics/network-analytics" product="networking-services" />

src/content/docs/magic-wan/analytics/query-bandwidth.mdx

@@ -8,4 +8,7 @@ sidebar:
 
 import { Render } from "~/components"
 
-<Render file="graphql/query-magic-transit-bandwidth-graphql" product="magic-transit" params={{ productName: "Magic WAN" }} />
+<Render file="graphql/query-magic-transit-bandwidth-graphql"
+	product="networking-services"
+	params={{ productName: "Magic WAN" }}
+/>

src/content/docs/magic-wan/analytics/query-tunnel-health.mdx

@@ -8,4 +8,6 @@ sidebar:
 
 import { Render } from "~/components"
 
-<Render file="graphql/query-magic-transit-health-checks" product="magic-transit" params={{ productName: "Magic WAN" }} />
+<Render file="graphql/query-magic-transit-health-checks"
+	product="networking-services"
+	params={{ productName: "Magic WAN" }} />

src/content/docs/magic-wan/analytics/traceroutes.mdx

@@ -7,4 +7,7 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="analytics/traceroutes" params={{ productName: "WAN" }} />
+<Render file="analytics/traceroutes"
+	product="networking-services"
+	params={{ productName: "WAN" }}
+/>

src/content/docs/magic-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx

@@ -8,7 +8,8 @@ sidebar:
 import { Render } from "~/components";
 
 <Render
-	file="tunnel-healthchecks-dash"
+	file="tunnel-health/check-tunnel-healthchecks-dash"
+	product="networking-services"
 	params={{
 		dashInfo:
 			"The dashboard shows the view of tunnel health as measured from each Cloudflare location where your traffic is likely to land.",

src/content/docs/magic-wan/configuration/common-settings/configure-magic-tunnel-alerts.mdx

@@ -8,7 +8,8 @@ description: Use the API to set up and configure Magic Tunnel health alerts
 import { Render } from "~/components";
 
 <Render
-	file="magic-tunnel-health-alerts/magic-tunnel-health-alerts"
+	file="tunnel-health/magic-tunnel-health-alerts"
+	product="networking-services"
 	params={{
 		magicWord: "Magic WAN",
 		productName: "Magic WAN",

src/content/docs/magic-wan/configuration/common-settings/enable-magic-roles.mdx

@@ -9,4 +9,4 @@ description: You can determine which users have, or do not have, configuration
 
 import { Render } from "~/components"
 
-<Render file="magic-user-role" product="magic-transit" />
+<Render file="magic-user-role" product="networking-services" />

src/content/docs/magic-wan/configuration/common-settings/tunnel-health-checks.mdx

@@ -9,7 +9,7 @@ import { Render } from "~/components";
 
 <Render
 	file="tunnel-health/update-tunnel-health-checks-frequency"
-	product="magic-transit"
+	product="networking-services"
 	params={{
 		magicProduct: "Magic WAN",
 		productName: "Magic WAN",

src/content/docs/magic-wan/configuration/connector/configure-hardware-connector/index.mdx

@@ -8,7 +8,9 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="connector/configure-connectors" params={{
+<Render file="mconn/configure-connectors"
+	product="networking-services"
+	params={{
 	magicWord: "hardware",
 	productName: "Magic WAN Connector",
 	wan: "refers to the physical Magic WAN Connector Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/magic-wan/configuration/connector/configure-hardware-connector/sfp-port-information/) for more information on the hardware supported.",

src/content/docs/magic-wan/configuration/connector/configure-virtual-connector.mdx

@@ -7,7 +7,9 @@ sidebar:
 
 import { Render } from "~/components";
 
-<Render file="connector/configure-connectors" params={{
+<Render file="mconn/configure-connectors"
+	product="networking-services"
+	params={{
 	magicWord: "virtual",
 	productName: "Virtual Connector",
 	wan: "needs to correspond to the virtual network interface on the Virtual Connector instance you have set up in VMware. Following our example from the previous steps, you need to choose port `1` since that is what corresponds to the `eno1` port we set up in VMware.",

src/content/docs/magic-wan/configuration/connector/network-options/application-based-policies/breakout-traffic.mdx

@@ -8,7 +8,9 @@ description: Breakout traffic allows you to define which applications should
 
 import { Render } from "~/components";
 
-<Render file="connector/app-aware-policies/breakout-prioritized" params={{
+<Render file="mconn/app-aware-policies/breakout-prioritized"
+	product="networking-services"
+	params={{
 	magicWord: "breakout",
 	featureName: "Breakout traffic",
 	whatHappensApp: "will now go directly to the Internet and bypass Cloudflare's filtering",

src/content/docs/magic-wan/configuration/connector/network-options/application-based-policies/prioritized-traffic.mdx

@@ -8,7 +8,9 @@ description: Prioritized traffic allows you to define which applications are
 
 import { Render } from "~/components";
 
-<Render file="connector/app-aware-policies/breakout-prioritized" params={{
+<Render file="mconn/app-aware-policies/breakout-prioritized"
+	product="networking-services"
+	params={{
 	magicWord: "prioritized",
 	featureName: "Prioritized traffic",
 	whatHappensApp: "is now processed first by Connector",

src/content/docs/magic-wan/configuration/connector/network-options/dhcp/dhcp-relay.mdx

@@ -42,7 +42,7 @@ To configure DHCP relay:
 
 </TabItem> <TabItem label="API">
 
-<Render file="connector/account-id-api-key" />
+<Render file="account-id-api-key" product="networking-services" />
 
 Create a [`PUT` request](/api/resources/magic_transit/subresources/sites/subresources/lans/methods/update/) to update the LAN where you want to enable DHCP relay: