Improvement for Matrix Fields: Use of Field Editor Instead of Clip View

[alexanderbuergin]

Description

I propose changing the input interface for Matrix fields from the current Clip view to the Field Editor, which is already used for all entry types.

Background

Matrix fields have essentially become similar to entry types, as they can now contain their own fields. By leveraging the existing Field Editor, which is already integrated into the system, the user experience (UX) can be significantly improved.

Advantages

• Improved Clarity: Matrix fields with many different input types (e.g., 15–20 or more) quickly become cluttered. By using tabs and the search functionality available in the Field Editor, this issue could be easily resolved.
• Reusability of Existing Features: Instead of developing a new UI component, we could rely on the existing Field Editor and its proven features, saving development time and ensuring consistency within the UI.
• Enhanced Structure: The Field Editor allows for logical grouping of fields, which would be especially helpful in managing large Matrix fields with many input masks (e.g., 25+ entry types).

Current Issues

• Matrix fields with many input types quickly become overwhelming, especially when they should be divided into groups. This issue remains unresolved.
• A plugin that partially addresses this issue already exists for Craft 5, but I believe this functionality should be part of the core of Craft CMS 5, particularly since Craft 5 is focusing on UX improvements in the backend.

This approach could solve many of the existing problems by utilizing already available elements and functionality.

Expected Behavior

By integrating the Field Editor for Matrix fields, the management and input of fields will become more intuitive, organized, and efficient. Grouping and searching will be directly integrated.

Images

[davidhellmann]

This should also be in the right color and have icons. Otherwise, agree!

[thupsi]

Nice idea!