Link fix

gatsby-config.js

@@ -585,22 +585,22 @@ module.exports = {
 
                     {
                         title: "Adobe Experience Platform Location Service",
-                        path: "/documentation/places",
+                        path: "/documentation/solution-extensions/places",
                         pages: [{
                                 title: "Overview",
-                                path: "/documentation/places"
+                                path: "/documentation/solution-extensions/places"
                             },
                             {
                                 title: "API reference",
-                                path: "documentation/places/api-reference.md"
+                                path: "documentation/solution-extensions/places/api-reference.md"
                             },
                             {
                                 title: "Event forwarding to Adobe Experience Platform",
-                                path: "documentation/places/places-to-platform.md"
+                                path: "documentation/solution-extensions/places/places-to-platform.md"
                             },
                             {
                                 title: "Release notes",
-                                path: "documentation/places/release-notes.md"
+                                path: "documentation/solution-extensions/places/release-notes.md"
                             }
                         ]
                     },

src/pages/documentation/base-extensions/mobile-core/api-reference.md

@@ -16,7 +16,7 @@ Programmatic updates made to the configuration can be cleared via the `clearUpda
 
 ## collectMessageInfo
 
-User interactions with local or push notifications can be tracked by invoking the `collectMessageInfo` API. Please refer to [this page](../../documentation/adobe-campaign-standard#tracking-local-and-push-notification-message-interactions) for more information about tracking local and push notification message interactions.
+User interactions with local or push notifications can be tracked by invoking the `collectMessageInfo` API. Please refer to [this page](../../solution-extensions/adobe-campaign-standard/index.md#tracking-local-and-push-notification-message-interactions) for more information about tracking local and push notification message interactions.
 
 ## collectLaunchInfo
 
@@ -128,7 +128,7 @@ iOS
 
 ## getPrivacyStatus
 
-You can use the `getPrivacyStatus` API to retrieve the current privacy status. For more information about privacy in Mobile Core, please see [Privacy and GDPR](../resources/privacy-and-gdpr.md#getprivacystatus)
+You can use the `getPrivacyStatus` API to retrieve the current privacy status. For more information about privacy in Mobile Core, please see [Privacy and GDPR](../../resources/privacy-and-gdpr.md#getprivacystatus)
 
 ## getSdkIdentities
 
@@ -147,7 +147,7 @@ To retrieve data as a JSON string from the SDKs and send this data to your serve
 
 <InlineAlert variant="warning" slots="text"/>
 
-You must call the API below and retrieve identities stored in the SDK, **before** the user opts out.<br/><br/>This API does **not** include the identities stored in the Edge Identity extension. To retrieve the identities from the Edge Identity extension, use [getIdentities](../identity-for-edge-network/api-reference.md#getidentities).
+You must call the API below and retrieve identities stored in the SDK, **before** the user opts out.<br/><br/>This API does **not** include the identities stored in the Edge Identity extension. To retrieve the identities from the Edge Identity extension, use [getIdentities](../../edge-extensions/identity-for-edge-network/api-reference.md#getidentities).
 
 <TabsBlock orientation="horizontal" slots="heading, content" repeat="2"/>
 
@@ -332,7 +332,7 @@ Flutter
 
 ## setPrivacyStatus
 
-You can use the `setPrivacyStatus` API to set the privacy status. For more information about privacy in Mobile Core, please see [Privacy and GDPR](../resources/privacy-and-gdpr.md#setprivacystatus) API's.
+You can use the `setPrivacyStatus` API to set the privacy status. For more information about privacy in Mobile Core, please see [Privacy and GDPR](../../resources/privacy-and-gdpr.md#setprivacystatus) API's.
 
 ## setPushIdentifier
 

src/pages/documentation/base-extensions/mobile-core/configuration/api-reference.md

@@ -58,7 +58,7 @@ iOS
 
 This API is only available in Android.
 
-You can bundle a JSON configuration file in the app's Assets folder to replace or complement the configuration that was downloaded by using the [Configure with App ID per environment](../#configure-with-app-id-per-environment) approach.
+You can bundle a JSON configuration file in the app's Assets folder to replace or complement the configuration that was downloaded by using the [Configure with App ID per environment](./index.md#configure-with-app-id-per-environment) approach.
 
 <TabsBlock orientation="horizontal" slots="heading, content" repeat="1"/>
 
@@ -68,7 +68,7 @@ Android
 
 ## configureWithFileInPath
 
-You can include a bundled JSON configuration file in your app package to replace or complement the configuration that was downloaded by using the [Configure with App ID per environment](../#configure-with-app-id-per-environment) approach.
+You can include a bundled JSON configuration file in your app package to replace or complement the configuration that was downloaded by using the [Configure with App ID per environment](./index.md#configure-with-app-id-per-environment) approach.
 
 To pass in a bundled path and file name:
 

src/pages/documentation/base-extensions/mobile-core/configuration/index.md

@@ -46,7 +46,7 @@ Keys that are not found on the current configuration are added when this method
 
 <InlineAlert variant="warning" slots="text"/>
 
-Do not use this API to update the build.environment or any key with an environment prefix, because it can lead to unexpected behavior. For more information, read [Environment-aware configuration properties](./index.md#environment-aware-configuration-properties).
+Do not use this API to update the build.environment or any key with an environment prefix, because it can lead to unexpected behavior. For more information, read [Environment-aware configuration properties](#environment-aware-configuration-properties).
 
 <TabsBlock orientation="horizontal" slots="heading, content" repeat="2"/>
 
@@ -74,7 +74,7 @@ For implementation details, please refer to [Configuration API reference](./api-
 
 ## Using a bundled file configuration
 
-You can include a bundled JSON configuration file in your app package to replace or complement the configuration that was downloaded by using the [Configure with App ID per environment](./index.md#configure-with-app-id-per-environment) approach.
+You can include a bundled JSON configuration file in your app package to replace or complement the configuration that was downloaded by using the [Configure with App ID per environment](#configure-with-app-id-per-environment) approach.
 
 To download the JSON configuration file, use the following URL:
 

src/pages/documentation/base-extensions/mobile-core/identity/api-reference.md

@@ -21,9 +21,9 @@ If the provided URL is null or empty, it is returned as is. Otherwise, the follo
 * The `adobe_mc` attribute is a URL encoded list that contains:
   * `MCMID` - Experience Cloud ID (ECID)
   * `MCORGID` - Experience Cloud Org ID
-  * `MCAID` - Analytics Tracking ID (AID), if available from the [Analytics extension](../../adobe-analytics/api-reference.md#gettrackingidentifier)
+  * `MCAID` - Analytics Tracking ID (AID), if available from the [Analytics extension](../../../solution-extensions/adobe-analytics/api-reference.md#gettrackingidentifier)
   * `TS` - A timestamp taken when this request was made
-* The optional `adobe_aa_vid` attribute is the URL-encoded Analytics Custom Visitor ID (VID), if previously set in the [Analytics extension](../../adobe-analytics/api-reference.md#setvisitoridentifier).
+* The optional `adobe_aa_vid` attribute is the URL-encoded Analytics Custom Visitor ID (VID), if previously set in the [Analytics extension](../../../solution-extensions/adobe-analytics/api-reference.md#setvisitoridentifier).
 
 This API is designed to handle the following URL formats:
 
@@ -154,9 +154,9 @@ If an error occurs while retrieving the URL string, the callback handler will be
 * The `adobe_mc` attribute is an URL encoded list that contains:
   * `MCMID` - Experience Cloud ID (ECID)
   * `MCORGID` - Experience Cloud Org ID
-  * `MCAID` - Analytics Tracking ID (AID), if available from the [Analytics extension](../../adobe-analytics/index.md)
+  * `MCAID` - Analytics Tracking ID (AID), if available from the [Analytics extension](../../../solution-extensions/adobe-analytics/index.md)
   * `TS` - A timestamp taken when this request was made
-* The optional `adobe_aa_vid` attribute is the URL-encoded Analytics Custom Visitor ID (VID), if previously set in the [Analytics extension](../../adobe-analytics/index.md).
+* The optional `adobe_aa_vid` attribute is the URL-encoded Analytics Custom Visitor ID (VID), if previously set in the [Analytics extension](../../../solution-extensions/adobe-analytics/index.md).
 
 <TabsBlock orientation="horizontal" slots="heading, content" repeat="2"/>
 
@@ -180,7 +180,7 @@ Flutter
 
 <InlineAlert variant="warning" slots="text"/>
 
-This API is only available in Android and is deprecated starting in version 2.0.0 of the Identity extension. Use [`MobileCore.registerExtensions()`](../../api-reference.md#registerextensions) instead.
+This API is only available in Android and is deprecated starting in version 2.0.0 of the Identity extension. Use [`MobileCore.registerExtensions()`](../api-reference.md#registerextensions) instead.
 
 The `registerExtension()` API registers the Identity extension with the Mobile Core extension. This API allows the extension to send and receive events to and from the Mobile SDK.
 
@@ -203,11 +203,11 @@ Some example use cases for this API are:
 
 This API is **not** recommended for:
 
-* Resetting a user's privacy settings; see [Privacy and GDPR](../../resources/privacy-and-gdpr.md).
+* Resetting a user's privacy settings; see [Privacy and GDPR](../../../resources/privacy-and-gdpr.md).
 * Removing existing custom identifiers; use the [`syncIdentifier`](#syncidentifier) API instead.
 * Removing a previously synced advertising identifier after the advertising tracking settings were changed by the user; use the [`setAdvertisingIdentifier`](#setadvertisingidentifier) API instead.
 
-See [`MobileCore.resetIdentities`](../../api-reference.md#resetidentities) for more details.
+See [`MobileCore.resetIdentities`](../api-reference.md#resetidentities) for more details.
 
 ## setAdvertisingIdentifier
 

src/pages/documentation/base-extensions/mobile-core/identity/push-sync.md

@@ -70,7 +70,7 @@ Launch your app with the device connected to an [Adobe Experience Platform Assur
 In the list of events, verify that you have an event with type `UPDATED_IDENTITY_RESPONSE`. In the details panel on the right, confirm that the following values are correct:
 
 * The value for `pushidentifier` should match the value that was sent in step 2 above.
-* The value for mid should match the value for mid that is sent to Analytics. If you are using a [custom visitor identifier](../adobe-analytics/api-reference.md#setidentifier), this payload should also contain a vid variable with a value that matches the value that was used to identify this user.
+* The value for mid should match the value for mid that is sent to Analytics. If you are using a [custom visitor identifier](../../../solution-extensions/adobe-analytics/api-reference.md#setidentifier), this payload should also contain a vid variable with a value that matches the value that was used to identify this user.
 
 ![Verify push identifier synced](./assets/push-sync/push-identities.png)
 

src/pages/documentation/base-extensions/mobile-core/lifecycle/api-reference.md

@@ -84,7 +84,7 @@ iOS
 
 <InlineAlert variant="warning" slots="text"/>
 
-Deprecated as of 2.0.0. Please use the [MobileCore.registerExtensions](../../api-reference.md#registerextensions) API instead.
+Deprecated as of 2.0.0. Please use the [MobileCore.registerExtensions](../api-reference.md#registerextensions) API instead.
 
 Registers the Lifecycle extension with the Mobile Core.
 

src/pages/documentation/base-extensions/mobile-core/lifecycle/event-reference.md

@@ -96,7 +96,7 @@ This event is a response from the Lifecycle extension to notify that the applica
 
 <InlineAlert variant="info" slots="text"/>
 
-To forward this event to the Adobe Experience Platform Edge Network, follow the steps outlined in [Configure a Rule to forward Lifecycle metrics to Platform](../../lifecycle-for-edge-network/index.md#configure-a-rule-to-forward-lifecycle-metrics-to-platform).
+To forward this event to the Adobe Experience Platform Edge Network, follow the steps outlined in [Configure a Rule to forward Lifecycle metrics to Platform](../../../edge-extensions/lifecycle-for-edge-network/index.md#configure-a-rule-to-forward-lifecycle-metrics-to-platform).
 
 <InlineAlert variant="info" slots="text"/>
 
@@ -110,7 +110,7 @@ In Android, there is a 500 millisecond timeout between consecutive `lifecycleSta
 
 #### Data payload
 
-The Lifecycle application foreground data payload is defined by the Platform Mobile Lifecycle Details XDM field group, and includes information about the application, device, and environment when the event occurred. Please refer to [Lifecycle Application Foreground metrics](../../lifecycle-for-edge-network/metrics.md#lifecycle-application-foreground-metrics) for a list of metrics included with this event.
+The Lifecycle application foreground data payload is defined by the Platform Mobile Lifecycle Details XDM field group, and includes information about the application, device, and environment when the event occurred. Please refer to [Lifecycle Application Foreground metrics](../../../edge-extensions/lifecycle-for-edge-network/metrics.md#lifecycle-application-foreground-metrics) for a list of metrics included with this event.
 
 ### Lifecycle application background
 
@@ -123,7 +123,7 @@ The event is generated by the Lifecycle extension when:
 
 <InlineAlert variant="info" slots="text"/>
 
-To forward this event to the Adobe Experience Platform Edge Network, follow the steps outlined in [Configure a Rule to forward Lifecycle metrics to Platform](../../lifecycle-for-edge-network/index.md#configure-a-rule-to-forward-lifecycle-metrics-to-platform).
+To forward this event to the Adobe Experience Platform Edge Network, follow the steps outlined in [Configure a Rule to forward Lifecycle metrics to Platform](../../../edge-extensions/lifecycle-for-edge-network/index.md#configure-a-rule-to-forward-lifecycle-metrics-to-platform).
 
 <InlineAlert variant="info" slots="text"/>
 
@@ -137,4 +137,4 @@ In Android, there is a 500 millisecond timeout between consecutive `lifecycleSta
 
 #### Data payload
 
-The Lifecycle Application Background data payload is defined by the Platform Mobile Lifecycle Details XDM field group, and includes information about the application close type and previous session length. Please refer to [Lifecycle Application Background metrics](../../lifecycle-for-edge-network/metrics.md#lifecycle-application-background-metrics) for a list of metrics included with this event.
+The Lifecycle Application Background data payload is defined by the Platform Mobile Lifecycle Details XDM field group, and includes information about the application close type and previous session length. Please refer to [Lifecycle Application Background metrics](../../../edge-extensions/lifecycle-for-edge-network/metrics.md#lifecycle-application-background-metrics) for a list of metrics included with this event.

src/pages/documentation/base-extensions/mobile-core/lifecycle/ios.md

@@ -12,7 +12,7 @@ keywords:
 
 <InlineAlert variant="warning" slots="text"/>
 
-In version 4 of the iOS SDK, this implementation was completed automatically. <br/><br/>When upgrading to the Experience Platform SDK, you must add code to continue collecting Lifecycle metrics. For more information, see [Manual Lifecycle Implementation](../../upgrade-platform-sdks/lifecycle.md).
+In version 4 of the iOS SDK, this implementation was completed automatically. <br/><br/>When upgrading to the Experience Platform SDK, you must add code to continue collecting Lifecycle metrics. For more information, see [Manual Lifecycle Implementation](../../../resources/upgrade-platform-sdks/lifecycle.md).
 
 ## Implementing Lifecycle metrics in iOS
 
@@ -45,7 +45,7 @@ The following scenarios are known to falsely cause a crash to be reported by the
 * If you are debugging using Xcode, re-launching the app while it is running in the foreground will cause a crash.
   * You can avoid a crash in this scenario by backgrounding the app prior to re-launching the app from Xcode.
 * If your app is launched in the background because of an enabled background capability (e.g. - background fetch, location update), then `lifecycleStart` is called and the app never comes to the foreground, the next launch (whether in the background or foreground) will result in a crash.
-* If you programmatically delete Adobe’s pause flag from `NSUserDefaults`, while the app is in the background, the next launch or resume causes a crash.
+* If you programmatically delete Adobe's pause flag from `NSUserDefaults`, while the app is in the background, the next launch or resume causes a crash.
 
 ### How can I prevent false crashes from being reported?
 

src/pages/documentation/base-extensions/mobile-core/lifecycle/tabs/index.md

@@ -10,7 +10,7 @@ Add the Lifecycle extension and its dependency, the [Mobile Core](../index.md) e
 
 <InlineNestedAlert variant="warning" header="false" iconPosition="left">
 
-Using dynamic dependency versions is **not** recommended for production apps. Please read the [managing Gradle dependencies guide](../resources/manage-gradle-dependencies.md) for more information.
+Using dynamic dependency versions is **not** recommended for production apps. Please read the [managing Gradle dependencies guide](../../../resources/manage-gradle-dependencies.md) for more information.
 
 </InlineNestedAlert>
 

src/pages/documentation/base-extensions/mobile-core/rules-engine/consequence-details.md

@@ -17,7 +17,7 @@ The Adobe Experience Platform Mobile SDK supports multiple types of rule consequ
 
 ## Analytics consequence
 
-This rule consequence is currently handled by the [Analytics](../../adobe-analytics/index.md) extension.
+This rule consequence is currently handled by the [Analytics](../../../solution-extensions/adobe-analytics/index.md) extension.
 
 | Friendly name | Key | Type | Required | Description |
 | :--- | :--- | :--- | :--- | :--- |
@@ -27,7 +27,7 @@ This rule consequence is currently handled by the [Analytics](../../adobe-analyt
 
 ## In-App message consequence
 
-This rule consequence is currently handled by the [Campaign](../../adobe-campaign-standard/index.md) extension.
+This rule consequence is currently handled by the [Campaign](../../../solution-extensions/adobe-campaign-standard/index.md) extension.
 
 | Friendly name | Key | Type | Required | Description |
 | :--- | :--- | :--- | :--- | :--- |
@@ -92,4 +92,4 @@ This rule is currently handled by the [Mobile Core](../index.md) extension.
 
 | Friendly name | Key | Type | Required | Description |
 | :--- | :--- | :--- | :--- | :--- |
-| Event data | `eventdata` | object | Yes | Dictionary of pairs to overlay on the triggering event's EventData. For more information, see the [attach data tutorial](../../user-guides/attach-data.md). |
+| Event data | `eventdata` | object | Yes | Dictionary of pairs to overlay on the triggering event's EventData. For more information, see the [attach data tutorial](../../../resources/user-guides/attach-data.md). |

src/pages/documentation/base-extensions/mobile-core/signal/api-reference.md

@@ -40,7 +40,7 @@ Flutter
 
 <InlineAlert variant="warning" slots="text"/>
 
-Deprecated as of 2.0.0. Please use the [MobileCore.registerExtensions](../../api-reference.md#registerextensions) API instead.
+Deprecated as of 2.0.0. Please use the [MobileCore.registerExtensions](../api-reference.md#registerextensions) API instead.
 
 Registers the Signal extension with the Mobile Core.
 
@@ -56,4 +56,4 @@ Android
 
 ## collectPii
 
-The Signal extension can be used to handle `collectPii` rules. For more information, see the [collectPii](../../api-reference.md#collectpii) API.
+The Signal extension can be used to handle `collectPii` rules. For more information, see the [collectPii](../api-reference.md#collectpii) API.