For both marketers and developers, it could be very useful to have the ability to contribute content from their tablet and mobile. To do that, the user interface needs to be responsive and adaptive to every device sizes.

Summary The current and previous (v3) WYSIWYG editor are more so basic markdown editors and while markdown is awesome (since I'm writing this feature request in markdown smile ) I believe there is room for improvement and we could swap the default editor shipped with Strapi for something more feature rich and complete. There is already community options in both v3 and v4 such as CKEditor 5, React MD, Toast UI, and Editor.js I do think we should ship something more feature complete then forcing everyone to install one of the community options. If anything we could also make it easier to swap out our editor by standardizing methods to build new editors into the Strapi interface. Why is it needed? Our current editor only supports the bare minimums in terms of markdown support (eg no tables, ect) and support for things like inline youtube video previews, ect are a bit more complex to handle properly. Likewise not all non-technical content editors are familiar or like markdown. Likewise in many frontend frameworks a library is required to convert markdown to html. I believe it could be possible to handle this type of conversion server side and maybe caching those outputs (or pregenerating them). see: https://github.com/strapi/strapi/issues/12440

Display a field only if some conditions are met.

Allow users to manage content by having a published and draft content at the same time.

While you edit a blog post, you might associate it to a brand new category. Unfortunately, if the category doesn't exist, you have to save the post. Create the category. Then go back to the post to attach it the category. Until we release this functionality to create new entry on-the-fly on top of the relation fields. https://github.com/strapi/strapi/pull/5125

When having an i18n enabled collection and you duplicate an item through the Content Manager it only copies the default language's translation. See: https://github.com/strapi/strapi/issues/13584

Somewhat related to the previous suggestion I made ( https://feedback.strapi.io/customization/p/allow-sort-order-to-be-applied-to-internationalization-locales-in-content-manage ), make the default selected locale when you open the "Fill in from another locale" modal on a content item be the default locale rather than whatever locale happens to be first when sorted by numeric ID.

It could be great to add context or let the users create their contents with little constraints. For example, a grid could have differents components inside like download cards or profile cards. Making a grid component for each variation is not optimal so it would make the UI clearer with fewer components. Lastly, the front-end developer could develop a component manager from front-end and it would manage all content to build the website like legos. The developer would maintain the content builder from strapi POV and the users can immediately use the news components or make change on already launched content.

Add option to create copies for uploaded images in webp and avif. By default the plugin should keep it's behaviour and not convert uploads. But if its configuration is enabled to convert, it should save an additional copy for each breakpoint in every enabled image type. This two image type formats are very useful to improve web loading time. See: https://github.com/strapi/strapi/issues/10420

see: https://github.com/strapi/strapi/issues/557