Skip to content

Commit c147383

Browse files
authored
Merge pull request AdobeDocs#296 from mariam21arauj/CEXT-3900
Migrating from application to extension and Admin UI SDK compatibility
2 parents 70fd4c4 + 14ddc9b commit c147383

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,3 +33,9 @@ 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+
Adobe App Builder supports [extensions](https://developer.adobe.com/app-builder/docs/guides/extensions/), which allow developers to integrate their applications with specific Adobe products, such as the Admin UI SDK. Extensions act as a bridge between Adobe products and the applications built using Adobe App Builder. As a result, these applications can be easily integrated and extended within Adobe's ecosystem.
40+
41+
App Builder projects support `application` and `extension` configurations within the `app.config.yaml` file. The Admin UI SDK supports both of these types as well. The SDK is not affected if you [migrate](https://developer.adobe.com/app-builder/docs/guides/extensions/extension_migration_guide/) an existing App Builder project that uses an `application` configuration to use an `extension` configuration.

0 commit comments

Comments
 (0)