Reorganize Fields in Admin Forms for Improved Performance

Is your feature request related to a problem? Please describe.
The current structure of admin forms presents a significant performance issue. In forms with multiple WYSIWYG (What-You-See-Is-What-You-Get) fields, each instance of these fields is multiplied by the number of available languages. For example, if a form has 4-6 WYSIWYG fields, and there are multiple languages enabled, this results in dozens of WYSIWYG instances being loaded simultaneously. This leads to slower loading times, impeding efficient resource management for admins.

Describe the solution you'd like
We propose reorganizing the admin form structure to improve loading performance by:

• Reducing the number of WYSIWYG editors displayed on a single page.

• Dividing longer forms into multiple pages or sections, thereby allowing sections to load only when accessed.

• Loading only essential fields initially and deferring less-used fields until necessary to minimize data requests and improve responsiveness.

This adjustment would enable a more manageable number of WYSIWYG instances per page, significantly reducing the initial load time and enhancing admin efficiency.

Describe alternatives you've considered
Lazy Loading of WYSIWYG Fields: Enabling WYSIWYG fields to load only when scrolled into view. However, this would still strain system resources on larger forms with multiple fields and languages.

1. Switch to Simplified Text Fields: Replacing WYSIWYG editors with simpler text fields. This approach, however, limits rich-text formatting options that are necessary for some content creation needs.

2. Separate Language-Specific Forms: Creating separate forms for each language. However, this could become cumbersome for admins managing multiple languages in a single session.

Additional context
The proposed restructuring would allow smoother navigation and faster load times for admins, helping them to focus on resource management without delays. This is especially critical for high-traffic platforms with extensive language support. Visual layouts of the proposed multi-section forms and examples of the current vs. proposed load times would be beneficial for understanding the impact of the change.

Does this issue could impact on users private data?
No, this feature does not directly impact users' private data. It only modifies the layout and loading behavior of fields in admin forms.

Funded by
European Commission