Skip to content

Commit ce2f7ca

Browse files
committed
addsinformation on migrating from application to extension
1 parent 36284f4 commit ce2f7ca

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

src/pages/admin-ui-sdk/index.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,3 +33,11 @@ The following sequence diagram illustrates the authentication process.
3333
## Code samples
3434

3535
The [Adobe Commerce Samples repository](https://github.com/adobe/adobe-commerce-samples/tree/main/admin-ui-sdk) contains samples for different extension points of the Adobe Commerce Admin UI SDK. Use these samples to gain insight on how the Admin SDK injects menus and pages into the Admin.
36+
37+
## Admin UI SDK and Adobe Extensions
38+
39+
[Extensions] (https://developer.adobe.com/app-builder/docs/guides/extensions/) are a new feature in Adobe App Builder that allows developers to integrate their applications with specific Adobe products in a more seamless and unified manner.
40+
41+
In essence, extensions act as a bridge between Adobe products and the applications built using Adobe App Builder, ensuring that these applications can be easily integrated and extended within Adobe's ecosystem.
42+
43+
If you're [migrating] (https://developer.adobe.com/app-builder/docs/guides/extensions/extension_migration_guide/) an existing App Builder project that uses an `application` configuration in the `app.config.yaml` file to use an `extension` configuration, rest assured that this change will not cause any compatibility issues with your application and the Admin UI SDK. This switch is fully supported and will not affect your current application’s behavior.

0 commit comments

Comments
 (0)