Merge pull request #424 from calebk1/edge-split

Edge split - WIP

.github/scripts/update-release-notes.js

@@ -101,7 +101,7 @@ var reqGet = https.request(options, function(res) {
                         const monthNames = ["January", "February", "March", "April", "May", "June", "July", "August", "September", "October","November","December"]
                         const fullMonth = monthNames[month]
 
-                        const releaseMdPath = "./src/pages/documentation/release-notes/index.md";
+                        const releaseMdPath = "./src/pages/home/release-notes/index.md";
 
                         const releaseNotesHeader = "# Release notes";
                         // Read the contents of the markdown file.
@@ -166,7 +166,7 @@ function updateBOMReleaseNotesForAdobeIO(releaseNotesString) {
 
 function releaseFileContainsLineStartWith(lineStartWithString){
     try {
-        execSync(`grep -E "^${lineStartWithString}" ./src/pages/documentation/release-notes/index.md`, { stdio: 'ignore' });
+        execSync(`grep -E "^${lineStartWithString}" ./src/pages/home/release-notes/index.md`, { stdio: 'ignore' });
         return true;
       } catch (e) {
         return false;

.github/workflows/release-pr.yml

@@ -43,11 +43,11 @@ jobs:
 
       - name: Check release-notes/index.md
         run: |
-          if git diff --exit-code ./src/pages/documentation/release-notes/index.md; then
+          if git diff --exit-code ./src/pages/home/release-notes/index.md; then
             gh run cancel ${{ github.run_id }}
             gh run watch ${{ github.run_id }}
           else
-            echo "./src/pages/documentation/release-notes/index.md -> no update"
+            echo "./src/pages/home/release-notes/index.md -> no update"
           fi
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

src/pages/documentation/adobe-journey-optimizer-decisioning/api-reference.md → src/pages/edge/adobe-journey-optimizer-decisioning/api-reference.md

@@ -70,7 +70,7 @@ iOS
 
 <InlineAlert variant="warning" slots="text"/>
 
-Deprecated as of 2.0.0. Please use the [MobileCore.registerExtensions](../mobile-core/api-reference.md#registerextensions) API instead.
+Deprecated as of 2.0.0. Please use the [MobileCore.registerExtensions](../../home/base/mobile-core/api-reference.md#registerextensions) API instead.
 
 <TabsBlock orientation="horizontal" slots="heading, content" repeat="1"/>
 
@@ -85,7 +85,7 @@ Android
 This API call can lead to unintended SDK behavior, e.g. resetting of Experience Cloud ID (ECID). So it should be sparingly used and caution should be followed!
 
 This `MobileCore` API is a request to each extension to reset its identities. Every extension responds to this request in its own unique manner. For example, Optimize extension uses this API call to clear out its client-side in-memory propositions cache.
-For details on syntax, usage and availability, refer to [Mobile Core - Reset identities](../mobile-core/api-reference.md#resetidentities).
+For details on syntax, usage and availability, refer to [Mobile Core - Reset identities](../../home/base/mobile-core/api-reference.md#resetidentities).
 
 ## updatePropositions
 

src/pages/documentation/adobe-journey-optimizer-decisioning/index.md → src/pages/edge/adobe-journey-optimizer-decisioning/index.md

@@ -24,7 +24,7 @@ Before starting, make sure the following steps are completed.
 
 ### Configure the Datastream for Adobe Target and/or Journey Optimizer - Offer Decisioning
 
-On [Experience Platform Data Collection](https://experience.adobe.com/#/data-collection/), navigate to **Data Collection** > **Datatreams** using the left navigation panel. Select an existing datastream or create a new datastream. For more details, see the [configure datastreams guide](../getting-started/configure-datastreams.md).
+On [Experience Platform Data Collection](https://experience.adobe.com/#/data-collection/), navigate to **Data Collection** > **Datatreams** using the left navigation panel. Select an existing datastream or create a new datastream. For more details, see the [configure datastreams guide](../../home/getting-started/configure-datastreams.md).
 
 1. In the datastream, click on the desired environment from the list. Make sure **Adobe Experience Platform** section is enabled and configured with the required information like **Sandbox** and **Event Dataset**.
 2. For Journey Optimizer - Offer Decisioning, navigate to **Adobe Experience Platform** section and enable **Offer Decisioning** checkbox.
@@ -40,15 +40,15 @@ On [Experience Platform Data Collection](https://experience.adobe.com/#/data-col
 1. In your mobile property, navigate to **Extensions** in the left navigation panel and click on the **Catalog** tab.
 2. In the extensions Catalog, search or locate the **Adobe Journey Optimizer - Decisioning** extension, and click **Install**.
 3. Since an extension configuration is not necessary, click **Save**.
-4. Follow the publishing process to update SDK configuration. For more details, see the [publish the configuration guide](../getting-started/create-a-mobile-property.md.md#publish-the-configuration).
+4. Follow the publishing process to update SDK configuration. For more details, see the [publish the configuration guide](../../home/getting-started/create-a-mobile-property.md#publish-the-configuration).
 
 ![Adobe Journey Optimizer - Decisioning extension configuration](./assets/index/configuration.png)
 
 ## Integrate Experience Platform Optimize SDK in your mobile application
 
 <InlineAlert variant="warning" slots="text"/>
 
-For the AEPOptimize APIs to work properly, you need to integrate Mobile Core and Edge extensions in your mobile app. For more details see, documentation on [Mobile Core](../mobile-core/index.md) and [Adobe Experience Platform Edge Network](../edge-network/index.md).
+For the AEPOptimize APIs to work properly, you need to integrate Mobile Core and Edge extensions in your mobile app. For more details see, documentation on [Mobile Core](../../home/base/mobile-core/index.md) and [Adobe Experience Platform Edge Network](../../edge/edge-network/index.md).
 
 ### Install the Experience Platform Mobile SDK
 
@@ -143,7 +143,7 @@ To use Target Third Party ID in the Experience Edge mobile workflows, the corres
 
 ![Target Third Party ID configuration](./assets/index/target-tpid.png)
 
-In your mobile application, integrate the Identity for Edge Network extension to add the Target Third Party ID in the Identity Map in the personalization query request to the Edge network when calling the `updatePropositions` API. For more details, see the [Identity for Edge Network - updateIdentities API](../identity-for-edge-network/api-reference.md#updateidentities).
+In your mobile application, integrate the Identity for Edge Network extension to add the Target Third Party ID in the Identity Map in the personalization query request to the Edge network when calling the `updatePropositions` API. For more details, see the [Identity for Edge Network - updateIdentities API](../../edge/identity-for-edge-network/api-reference.md#updateidentities).
 
 <TabsBlock orientation="horizontal" slots="heading, content" repeat="2"/>
 
@@ -227,7 +227,7 @@ After you finish your rule configuration, verify the rule details are as shown b
 ![Adobe Journey Optimizer - Decisioning extension Lifecycle rule Configuration](./assets/index/lifecycle-rule.png)
 
 1. Click on **Save**.
-2. [Republish your configuration](../getting-started/create-a-mobile-property.md#publish-the-configuration) to the desired environment.
+2. [Republish your configuration](../../home/getting-started/create-a-mobile-property.md#publish-the-configuration) to the desired environment.
 
 ### Analytics for Target (A4T)
 
@@ -283,7 +283,7 @@ iOS
 
 <Tabs query="platform=ios&task=proposition-tracking-edge"/>
 
-The Edge `sendEvent` API can then be used to send this tracking XDM data along with any additional XDM and freeform data to the Experience Edge network. Additionally, an override dataset can also be specified for tracking data. For more details, see [Edge - sendEvent API](../edge-network/api-reference.md#sendevent).
+The Edge `sendEvent` API can then be used to send this tracking XDM data along with any additional XDM and freeform data to the Experience Edge network. Additionally, an override dataset can also be specified for tracking data. For more details, see [Edge - sendEvent API](../../edge/edge-network/api-reference.md#sendevent).
 
 <TabsBlock orientation="horizontal" slots="heading, content" repeat="2"/>
 
@@ -297,12 +297,12 @@ iOS
 
 ## Configuration keys
 
-To update the SDK configuration programmatically, use the following information to change the Optimize extension configuration values. For more information, see the [programmatic updates to Configuration guide](../mobile-core/configuration/api-reference.md#updateconfiguration).
+To update the SDK configuration programmatically, use the following information to change the Optimize extension configuration values. For more information, see the [programmatic updates to Configuration guide](../../home/base/mobile-core/configuration/api-reference.md#updateconfiguration).
 
 | Key | Required | Description | Data Type |
 | :--- | :--- | :--- | :--- |
 | optimize.datasetId | No | Override dataset's Identifier which can be obtained from the Experience Platform UI. For more details see, [Datasets UI guide](https://experienceleague.adobe.com/docs/experience-platform/catalog/datasets/user-guide.html) | String |
 
 <InlineAlert variant="info" slots="text"/>
 
-If the override dataset is used for proposition tracking, make sure the corresponding schema definition contains the `Experience Event - Proposition Interaction` field group. For more information, see the [setup schemas and datasets guide](../getting-started/set-up-schemas-and-datasets.md).
+If the override dataset is used for proposition tracking, make sure the corresponding schema definition contains the `Experience Event - Proposition Interaction` field group. For more information, see the [setup schemas and datasets guide](../../home/getting-started/set-up-schemas-and-datasets.md).