Support for Custom Field Types in Cloud Manager Content Fragment Editor

[#1]

Idea Summary: The new Cloud Manager Content Fragment (CF) Editor does not support displaying custom field types such as ColorField, TextArea, and PathField, which were previously replaced in the classic editor. This lack of support significantly impacts users relying on these customizations for structured content authoring. We propose adding native support or a UI extensibility option to render these field types appropriately.

Business Use Case: Organizations using AEM depend on custom field types to maintain structured content entry consistency. The inability to render these fields in the new CF Editor forces users to revert to the classic editor, limiting their ability to leverage new UI features. Providing native support for custom client-side renderers would enhance usability and encourage migration to the new UI.

Current Behavior:

• The CF Editor does not recognize or display custom fields such as ColorField, TextArea, and PathField.

• Custom client-side renderers are ignored, making values stored in these fields inaccessible.

• Users must use the classic editor to maintain content integrity, reducing the adoption of the new UI.

Expected Behavior:

• Support for rendering custom field types within the new CF Editor.

• The ability to register and reference custom client-side renderers for field visualization.

• Improved UI extensibility to maintain parity with the classic editor’s capabilities.

Steps to Reproduce:

1. Replace a single-line text field with a ColorField, TextArea, or PathField.

2. Open the Content Fragment in the new CF Editor.

3. Observe that the field does not render as expected.

4. Open the same fragment in the classic editor and see the expected rendering.

Impact & Benefits:

• Ensures a seamless transition from the classic editor to the new UI.

• Improves content authoring experience by maintaining structured field visualizations.

• Encourages adoption of the new CF Editor without sacrificing customization.

We appreciate Adobe’s continued improvements and request consideration for this enhancement in a future release. Thank you for reviewing this proposal.

[#2]

@HamzaBE2 

Thanks for proposing this idea.

This has been reported to the engineering under the internal reference SITES-29237. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.