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.

It would be really beneficial if there was a way to retain the order (using order column for example) of a collection and be able to update it via drag-and-drop on the collection view. There are many cases when we want to have a certain order of items (regardless of insert order/id/filter/sort options provided in the view), and to be able to retrieve the data using the predefined order later (as seen in the collection view for example) Using drag and drop would help as it's really tedious to go to a huge collection and pump the order column of each item (for a CMS user) or run a query on the database (for CMS power user) most common use case, ordering an employee list on a company website (or add a new employee at a specific position) see: https://github.com/strapi/strapi/issues/3946

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.

You often need to calculate or aggregate field together like you would do in a sheet: SUM(price,fees), DAYSAGO(date) or MULTIPLY (width, height). See the issue for more details: https://github.com/strapi/strapi/issues/3131

Images uploaded straight from the camera are displayed rotated. There is a setting in the media library to rotate images, but it is turned off by default. I’d argue that correctly rotated images should be the default. Steps to reproduce the behavior Take a picture with your phone camera Upload image to Strapi See rotated image Expected behavior Image rotation is calculated correctly by default. See: https://github.com/strapi/strapi/issues/12204

It is impossible to identify which media fields are multi-media; See: https://github.com/strapi/strapi/issues/10525

When deleting a localized entry on 3.6.2 there's a pop up saying it will delete "This will delete the active locale versions" (plural): Unsure whether this is should be a bug report or a feature request, since the message in the popup is ambiguous. It's unclear whether it tries to tell me that it's going to delete "the currently selected locale" or "all locales which are active in the plugin". In any case, it's doing the former and only deletes the currently selected locale in the overview. From what I've seen there doesn't appear to be an option to delete all localizations at once. See: https://github.com/strapi/strapi/issues/10411

Strapi doesn't show any reaction if component fields (in my case a repeatable one) are set as required field, but were not filled with data or were not add/created at all. Steps to reproduce the behavior Create collection type with a component, which in my case contains a text field and a relation field Click on the created comonent inside your collection type -> advanced settings -> required field create your collection type entry and do NOT create a component or add values to it. Nothing will happen if you click on save! A workaround in my case would be to set the relational field inside the component as required, but this doesn't work either, because there has been an issue for a long time with this too #557 Expected behavior Some working input validation, which highlights the component/field and/or shows a message, that it is required. See: https://github.com/strapi/strapi/issues/10030