Migration to flat unique document slugs independent from any parent document slug

docs/ref-arch/RA0001/1-event-driven-arch/readme.md

@@ -1,9 +1,7 @@
 ---
-id: id-ra0001-1
-slug: /ref-arch/fbdc46aaae/1
+id: 59c1f6
+slug: /ref-arch/59c1f6
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: Introduction and SAP's EDA Strategy
 description: >-
   Explore event-driven architecture concepts and building blocks for scalable

docs/ref-arch/RA0001/2-design-considerations/readme.md

@@ -1,9 +1,7 @@
 ---
-id: id-ra0001-2
-slug: /ref-arch/fbdc46aaae/2
+id: ee6233
+slug: /ref-arch/ee6233
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: Design Considerations for EDA Applications
 description: >-
   Understand key challenges, key design patterns and key considerations from
@@ -148,4 +146,4 @@ Go to [Integration with Amazon Web Services](../5-aws-iot-integration/readme.md)
 
 ### Architecture 2 - Event-driven architecture with Microsoft Azure as the Event Producer
 
-Go to [Integration with Microsoft Azure](../6-azure-iot-integration/readme.md)
+Go to [Integration with Microsoft Azure](../6-azure-iot-integration/readme.md)

docs/ref-arch/RA0001/3-sap-eda-patterns/readme.md

@@ -1,17 +1,14 @@
 ---
-id: id-ra0001-3
-slug: /ref-arch/fbdc46aaae/3
+id: 6de922
+slug: /ref-arch/6de922
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: EDA Sample Use Cases
-description: >-
-  Event-driven architecture use cases to highlight real-world applications.
+description: Event-driven architecture use cases to highlight real-world applications.
 keywords:
   - sap
   - eda
   - integration
-sidebar_label:  EDA Sample Use Cases 
+sidebar_label: EDA Sample Use Cases
 image: img/ac-soc-med.png
 tags:
   - appdev
@@ -77,4 +74,4 @@ Below are some sample use case scenarios demonstrating the application of event-
 ![drawio](drawio/eda_eventhub.drawio)
 
 
-Note: Refer to additional use case patterns in [SAP Learning Journey -Discovering Event-Driven Integration with SAP Integration Suite,advanced event mesh](https://learning.sap.com/learning-journeys/discovering-event-driven-integration-with-sap-integration-suite-advanced-event-mesh/presenting-event-driven-architecture-use-cases_babe31d3-d20d-4370-8f02-2f277f8033d5)
+Note: Refer to additional use case patterns in [SAP Learning Journey -Discovering Event-Driven Integration with SAP Integration Suite,advanced event mesh](https://learning.sap.com/learning-journeys/discovering-event-driven-integration-with-sap-integration-suite-advanced-event-mesh/presenting-event-driven-architecture-use-cases_babe31d3-d20d-4370-8f02-2f277f8033d5)

docs/ref-arch/RA0001/4-e2b-framework/readme.md

@@ -1,12 +1,9 @@
 ---
-id: id-ra0001-4
-slug: /ref-arch/fbdc46aaae/4
+id: 2a28bd
+slug: /ref-arch/2a28bd
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: SAP CAP Framework for Events to Business Actions Integration
-description: >-
- Custom CAP Application framework to build event-driven applications in SAP BTP
+description: Custom CAP Application framework to build event-driven applications in SAP BTP
 keywords:
   - sap
   - aws iot integration
@@ -162,4 +159,4 @@ Below are some of the examples and scenarios where this framework has been lever
 ## Resources
 For more information related to this reference architecture, you can check out the following resources:
 
-- [SAP Samples | GitHub ](https://github.com/SAP-samples/btp-events-to-business-actions-framework)
+- [SAP Samples | GitHub ](https://github.com/SAP-samples/btp-events-to-business-actions-framework)

docs/ref-arch/RA0001/5-aws-iot-integration/readme.md

@@ -1,9 +1,7 @@
 ---
-id: id-ra0001-5
-slug: /ref-arch/fbdc46aaae/5
+id: '448754'
+slug: /ref-arch/448754
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: Build Events-to-Business Actions Scenarios with SAP BTP and AWS IoT SiteWise
 description: >-
   Create event-driven architecture with AWS IoT SiteWise and SAP BTP for
@@ -101,4 +99,4 @@ These are the technical prerequisites for integration between AWS IoT SiteWise,
 
 For detailed step by step information and to try out the integration, go to [GitHub Samples](https://github.com/SAP-samples/btp-events-to-business-actions-framework/tree/main/scenarios/Integration-with-AWS/IoTSiteWise)
 
-Refer to [Integrating Amazon Rekognition and SAP EHS with SAP BTP for PPE Detection](https://github.com/SAP-samples/btp-events-to-business-actions-framework/tree/main/scenarios/Integration-with-AWS/PPE) for another reference application implementation.
+Refer to [Integrating Amazon Rekognition and SAP EHS with SAP BTP for PPE Detection](https://github.com/SAP-samples/btp-events-to-business-actions-framework/tree/main/scenarios/Integration-with-AWS/PPE) for another reference application implementation.

docs/ref-arch/RA0001/6-azure-iot-integration/readme.md

@@ -1,9 +1,7 @@
 ---
-id: id-ra0001-6
-slug: /ref-arch/fbdc46aaae/6
+id: 988fb1
+slug: /ref-arch/988fb1
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: Build Events-to-Business Actions Scenarios with SAP BTP and Microsoft Azure
 description: >-
   Build event-driven applications with Azure IoT and SAP BTP for real-time
@@ -120,4 +118,4 @@ These are the technical prerequisites for integration between Azure IoT Central,
     - Service for configuring Azure IoT Central Application
     - Required for configuring device templates, event producers and event routing.
 
-For detailed step by step information and to try out the integration, go to [GitHub Samples](https://github.com/SAP-samples/btp-events-to-business-actions-framework)
+For detailed step by step information and to try out the integration, go to [GitHub Samples](https://github.com/SAP-samples/btp-events-to-business-actions-framework)

docs/ref-arch/RA0001/readme.md

@@ -1,13 +1,7 @@
 ---
-id: id-ra0001
-slug: /ref-arch/fbdc46aaae
+id: 196eba
+slug: /ref-arch/196eba
 sidebar_position: 20
-sidebar_custom_props:
-  category_index:
-    - integration
-    - appdev
-    - aws
-    - azure
 title: Designing Event-Driven Applications
 description: >-
   Guidance for developing applications based on Event-Driven Architecture (EDA)
@@ -155,4 +149,4 @@ For more information related to this reference architecture, you can check out t
 - [SAP Samples | GitHub ](https://github.com/SAP-samples/btp-events-to-business-actions-framework)
 - [Blog Collection | SAP Integration Suite, advanced event mesh](https://community.sap.com/t5/technology-blog-posts-by-sap/sap-integration-suite-advanced-event-mesh-blog-collection/ba-p/14111943)
 - [SAP Developers | Publish and Subscribe to Events in SAP Integration Suite, advanced event mesh](https://developers.sap.com/tutorials/pubsub-view-events.html#51cb3f1a-5861-4802-a4a1-2f154eb40e0b)
-- [SAP Learning Journey - Discovering Event-Driven Integration with SAP Integration Suite, Advanced Event Mesh](https://learning.sap.com/learning-journeys/discovering-event-driven-integration-with-sap-integration-suite-advanced-event-mesh/describing-sap-s-event-driven-ecosystem_ebe634bf-a91d-4276-b538-a3f4026c0f61)
+- [SAP Learning Journey - Discovering Event-Driven Integration with SAP Integration Suite, Advanced Event Mesh](https://learning.sap.com/learning-journeys/discovering-event-driven-integration-with-sap-integration-suite-advanced-event-mesh/describing-sap-s-event-driven-ecosystem_ebe634bf-a91d-4276-b538-a3f4026c0f61)

docs/ref-arch/RA0002/1-fundamentals/1-single-region-resiliency/readme.md

@@ -1,9 +1,7 @@
 ---
-id: id-ra0002-1-1
-slug: /ref-arch/81805673c0/1/1
+id: a134ec
+slug: /ref-arch/a134ec
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: Single-region resiliency
 description: How the single region resiliency works. What are the benefits and drawbacks.
 keywords:
@@ -70,4 +68,4 @@ By deploying services across multiple AZs, SAP BTP ensures that applications rem
 
 1. **Susceptibility to Regional Failures**: While Multi-AZ architecture provides high availability within a region, it remains vulnerable to region-wide disruptions such as natural disasters or significant outages that can impact all AZs in the region.
 2. **Geographic Limitations**: Multi-AZ deployments are confined to a single region, which may not deliver optimal performance for users distributed globally due to increased latency and potential network bottlenecks.
-3. **Compliance Challenges**: Certain regulatory requirements mandate data storage and processing within specific geographic boundaries. Multi-AZ architecture, being region-centric, may not fully address these compliance needs, particularly for disaster recovery (DR) scenarios.
+3. **Compliance Challenges**: Certain regulatory requirements mandate data storage and processing within specific geographic boundaries. Multi-AZ architecture, being region-centric, may not fully address these compliance needs, particularly for disaster recovery (DR) scenarios.

docs/ref-arch/RA0002/1-fundamentals/2-multi-region-resiliency/readme.md

@@ -1,9 +1,7 @@
 ---
-id: id-ra0002-1-2
-slug: /ref-arch/81805673c0/1/2
+id: 332db2
+slug: /ref-arch/332db2
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: Multi-region resiliency
 description: >-
   Learn how and why Multi-region resiliency ensures applications remain
@@ -109,4 +107,4 @@ Multi-region resiliency is essential not only for disaster recovery but also for
 
 3. **Cost Considerations**: Running services in multiple regions can increase infrastructure costs due to the need for redundant resources. Each region requires its own set of compute, storage, and networking resources, which can lead to higher operational expenses. Additionally, data transfer costs between regions can add up, especially for applications with high data synchronization requirements. Cost management strategies, such as using spot instances, optimizing resource allocation, and leveraging cloud provider cost management tools, are essential to control expenses in a multi-region setup.
 
-4. **Application Design**: Adapting applications for multi-region deployment may require architectural changes to handle data replication, failover, and latency. Applications must be designed to tolerate regional failures and ensure seamless failover to other regions. This often involves implementing stateless services, using distributed databases, and designing for eventual consistency. Additionally, applications must be optimized to minimize latency by routing user requests to the nearest region and efficiently handling cross-region data access. Architectural patterns like microservices, CQRS (Command Query Responsibility Segregation), and event-driven design can be beneficial in achieving these goals.
+4. **Application Design**: Adapting applications for multi-region deployment may require architectural changes to handle data replication, failover, and latency. Applications must be designed to tolerate regional failures and ensure seamless failover to other regions. This often involves implementing stateless services, using distributed databases, and designing for eventual consistency. Additionally, applications must be optimized to minimize latency by routing user requests to the nearest region and efficiently handling cross-region data access. Architectural patterns like microservices, CQRS (Command Query Responsibility Segregation), and event-driven design can be beneficial in achieving these goals.

docs/ref-arch/RA0002/1-fundamentals/readme.md

@@ -1,9 +1,7 @@
 ---
-id: id-ra0002-1
-slug: /ref-arch/81805673c0/1
+id: 33c25f
+slug: /ref-arch/33c25f
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: Single-region and Multi-region resiliency
 description: Overview for Single and Multi-region resiliency
 keywords:
@@ -26,7 +24,7 @@ toc_min_heading_level: 2
 toc_max_heading_level: 4
 draft: false
 unlisted: false
-contributors:
+contributors: 
 discussion: 
 last_update:
   author: arajsinha
@@ -37,4 +35,4 @@ last_update:
 - **[Single-region resiliency](1-single-region-resiliency/readme.md)**
 
 ## Multi-region resiliency configuration
-- **[Multi-region resiliency](2-multi-region-resiliency/readme.md)**
+- **[Multi-region resiliency](2-multi-region-resiliency/readme.md)**

docs/ref-arch/RA0002/2-geographic-redundancy/readme.md

@@ -1,9 +1,7 @@
 ---
-id: id-ra0002-2
-slug: /ref-arch/81805673c0/2
+id: cbc081
+slug: /ref-arch/cbc081
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: Geographic Redundancy
 description: >-
   Ensure continuous service with geographic redundancy for SAP BTP, distributing
@@ -70,4 +68,4 @@ Applications built using the SAP Cloud Application Programming Model (CAP) must
 
 While the multi-region architecture is viable for several SAP BTP services, challenges arise when stateful components such as a database or events come into play. Synchronizing these across regions requires numerous steps, adding complexity to the architecture. To simplify this orchestration process, we developed an open-source project called Multi-Region Manager, which functions as a control plane to manage synchronization, to control the failover and for other functionalities. Learn more about this here: [Multi-Region Manager](../6-control-plane/readme.md)
 
-These examples illustrate only a few of the SAP BTP services, and as new services/applications are need to adapt this architecture, a thorough analysis is necessary to ensure they are compliant with multi-region requirements. The priority and characteristics of each service will dictate the strategies required for achieving robust multi-region setup.
+These examples illustrate only a few of the SAP BTP services, and as new services/applications are need to adapt this architecture, a thorough analysis is necessary to ensure they are compliant with multi-region requirements. The priority and characteristics of each service will dictate the strategies required for achieving robust multi-region setup.

docs/ref-arch/RA0002/3-loadbalancers/readme.md

@@ -1,9 +1,7 @@
 ---
-id: id-ra0002-3
-slug: /ref-arch/81805673c0/3
+id: b66add
+slug: /ref-arch/b66add
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: Load Balancers
 description: >-
   Enhance SAP BTP setups with intelligent load balancing for optimal
@@ -125,4 +123,4 @@ The SAP Custom Domain Service allows organizations to map their own custom domai
 
 - [SAP Custom Domain service - SAP Help documentation](https://help.sap.com/docs/custom-domain/custom-domain-manager/what-is-custom-domain)
 - [SAP Custom Domain service configuration - Azure Traffic Manager for Multi-region architecture](https://github.com/SAP-samples/btp-services-intelligent-routing/tree/ci_azure/03-MapCustomDomainRoutes)
-- [SAP Custom Domain service configuration - AWS Route 53 for Multi-region architecture](https://github.com/SAP-samples/btp-services-intelligent-routing/tree/launchpad_aws/04-Map%20Custom%20Domain%20Routes)
+- [SAP Custom Domain service configuration - AWS Route 53 for Multi-region architecture](https://github.com/SAP-samples/btp-services-intelligent-routing/tree/launchpad_aws/04-Map%20Custom%20Domain%20Routes)

docs/ref-arch/RA0002/4-data-synchronization/readme.md

@@ -1,9 +1,7 @@
 ---
-id: id-ra0002-4
-slug: /ref-arch/81805673c0/4
+id: dd9a38
+slug: /ref-arch/dd9a38
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: Data Synchronization
 description: >-
   Ensure multi-region data consistency with SAP HANA Cloud's Smart Data Access
@@ -126,4 +124,4 @@ This comparative assessment provides valuable insights to assist decision-makers
 
 These steps can be time-consuming and may need to be repeated for multiple tables. Continuous monitoring is also necessary to address any unexpected issues promptly.
 
-To streamline this process, we developed an open-source project called **Multi-Region Manager**, which functions as a control plane to manage the SAP HANA Cloud synchronization, control the failover, and perform other functionalities. Learn more about it here: **[Multi-Region Manager for Orchestration](../RA0002/multi-region-manager)**. -->
+To streamline this process, we developed an open-source project called **Multi-Region Manager**, which functions as a control plane to manage the SAP HANA Cloud synchronization, control the failover, and perform other functionalities. Learn more about it here: **[Multi-Region Manager for Orchestration](../RA0002/multi-region-manager)**. -->

docs/ref-arch/RA0002/5-event-synchronization/readme.md

@@ -1,9 +1,7 @@
 ---
-id: id-ra0002-5
-slug: /ref-arch/81805673c0/5
+id: b6ca4c
+slug: /ref-arch/b6ca4c
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: Events Synchronization
 description: >-
   Enable resilient multi-region event processing with SAP Advanced Event Mesh,
@@ -97,4 +95,4 @@ The Advanced Event Mesh adapter enables the SAP Integration Suite to connect to
 
 These steps can be time-consuming and should ideally be automated. Continuous monitoring is also necessary to address any unexpected issues promptly.
 
-To streamline this process, we developed an open-source project called **Multi-Region Manager**. This tool functions as a control plane to manage SAP Advanced Event Mesh DMR clusters, handle replication, enable deploy/undeploy failover, control failover, and perform other functionalities. Learn more about it here: [Multi-Region Manager for Orchestration](../RA0002/multi-region-manager). -->
+To streamline this process, we developed an open-source project called **Multi-Region Manager**. This tool functions as a control plane to manage SAP Advanced Event Mesh DMR clusters, handle replication, enable deploy/undeploy failover, control failover, and perform other functionalities. Learn more about it here: [Multi-Region Manager for Orchestration](../RA0002/multi-region-manager). -->

docs/ref-arch/RA0002/6-control-plane/readme.md

@@ -1,9 +1,7 @@
 ---
-id: id-ra0002-6
-slug: /ref-arch/81805673c0/6
+id: 6cbe7d
+slug: /ref-arch/6cbe7d
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: Control Plane for Orchestration
 description: >-
   Ensure business continuity with Multi-Region Manager (MRM), orchestrating
@@ -69,4 +67,4 @@ To address these complex requirements and orchestrate multi-region process, a cu
 
  MRM is an open-source sample CAP-based application that can orchestrate the process of switching between regions. The orchestration process involves changes in replication topology, failover management, load balancer control, centralized monitoring and logging, and service-specific adaptations. It offers both manual and automatic failover options, requiring detailed analysis to choose the appropriate method based on the requirement. It can be deployed in both regions, so if one region is not available, the application could be accessed from the other region to initiate the failover.
 
-- [Multi-Region Manager implementation for SAP Cloud Integration flows](https://github.com/SAP-samples/btp-services-intelligent-routing/tree/ci_stateful_azure).
+- [Multi-Region Manager implementation for SAP Cloud Integration flows](https://github.com/SAP-samples/btp-services-intelligent-routing/tree/ci_stateful_azure).

docs/ref-arch/RA0002/7-sample-implementations/readme.md

@@ -1,9 +1,7 @@
 ---
-id: id-ra0002-7
-slug: /ref-arch/81805673c0/7
+id: cc4e29
+slug: /ref-arch/cc4e29
 sidebar_position: 1
-sidebar_custom_props:
-  category_index: []
 title: HA/DR Sample Implementations
 description: >-
   Implement HA/DR for SAP services using Azure Traffic Manager and AWS Route 53
@@ -76,4 +74,4 @@ Stateful scenarios necessitate the replication of data and events across regions
 
 Implement a stateful setup that requires data replication for internal state storage and document storage, utilizing SAP HANA Cloud, SAP Advanced Event Mesh, and Azure Traffic Manager. Also, replace regional JMS queues with SAP Advanced Event Mesh for disaster recovery.
 
-- **Implementation Overview**: [GitHub Repository](https://github.com/SAP-samples/btp-services-intelligent-routing/tree/ci_stateful_azure)
+- **Implementation Overview**: [GitHub Repository](https://github.com/SAP-samples/btp-services-intelligent-routing/tree/ci_stateful_azure)