Skip to content

[EPIC] Image Editor Feature Parity Migrate to Angular #34420

Description

@MariaFernandez778

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 ❌ No Not available — listed here because it reuses the same component

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

  • Developer teams
  • Content teams
  • DevOps teams
  • System administrators (dotCMS)

Links

Metadata

Metadata

Assignees

No one assigned

    Type

    No fields configured for Task.

    Projects

    Status
    In Progress

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions