Description
Migrate the legacy image editor in edit content from Dojo to Angular, displaying it on a dedicated page whenever launched from any existing entry point. The new page follows the Lara Theme design patterns.
Functionality remains the same as the legacy editor — with some tweaks — but the overall layout and design have changed.
🎨 Design: Image Editor — design spec
Field availability
The image editor uses a shared component across field types. Availability rules:
| Field type |
Image editor available? |
Notes |
| Binary Field |
✅ Only when the file is an image |
Hide the option for any non-image file type |
| Image Field |
✅ Yes |
Always available |
| File Field |
✅ Only when the file is an image |
Reuses the same component; the field references a file-asset content |
Image and File fields reference a file-asset contentlet, so saving an edited image checks in a new version of the referenced content. See #36363 for the implementation of editor availability in Image/File fields and the versioned save behavior.
Desired Outcome
Feature parity for the image editor in the new Angular-based edit content, with the editor correctly exposed/hidden per the field availability rules above.
Target Personas
Links
Description
Migrate the legacy image editor in edit content from Dojo to Angular, displaying it on a dedicated page whenever launched from any existing entry point. The new page follows the Lara Theme design patterns.
Functionality remains the same as the legacy editor — with some tweaks — but the overall layout and design have changed.
🎨 Design: Image Editor — design spec
Field availability
The image editor uses a shared component across field types. Availability rules:
Desired Outcome
Feature parity for the image editor in the new Angular-based edit content, with the editor correctly exposed/hidden per the field availability rules above.
Target Personas
Links