This repository contains a working example of the usage of UI Extensibility in AEM.
Through examples, we aim to demonstrate the potential of UI Extensibility and foster creativity.
Each folder contains a fully working UI Extension integrated with AEM.
In addition to git clone and/or forking this repo, you can generate an app from the @adobe/aio-cli
Example to generate the a button for CF Console:
aio app init --repo adobe/aem-uix-examples/cf-console-header-menu-button-sample
Here is the list of examples:
- Address Autocomplete
- Custom AEM Content Fragment Console Action Bar Button
- AEM Content Fragments Console Header Menu Button
- Customized AEM Content Fragment Editor Form Field
- AEM Content Fragment Editor Form Field Dropdown
- Custom AEM Content Fragment Editor RTE Toolbar Button
- Export Content Fragment to Adobe Target
- Content Fragment Language Copies Management
- Image genaration through 3rd party GenAI
- Slack Integration for Content Fragment management
- Workfront Task Management for Universal Editor
Each example has its own GitHub Actions deployment file that should be used as a starting point for individual extensions.
The root-level GitHub deployment file deploy_prod.yml is intended as a custom, all-in-one approach for deploying examples with stored secrets. Each example that needs to be deployed at a workspace must have an associated secret. For example, cf-console-action-bar-button-sample must have a secret named cf_console_action_bar_button_sample (with hyphens replaced by underscores) and the contents of the .env file as its value. Deployment will be triggered on merging PRs and push events on the main branch. Deployment will be skipped if this secret is unavailable.
Contributions are welcomed! Read the Contributing Guide for more information.
This project is licensed under the Apache V2 License. See LICENSE for more information.