Ordering Content Type entries in the List view
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
Dynamic Zone in Components
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.
Change Strapi's Default WYSIWYG to a more feature rich Editor
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
In many companies you're not alone to contribute and write content through the interface. However, it might happens that you need to check the content written by another author before publishing, or even translate the content in three languages... This plugin adds a powerful feature to set advanced contribution workflow in the interface.
DynamicZone - extend FriendlyName with MainValue like RepeatableComponent
The RepeatableComponent items easily distinctable by MainField, I think it should be used by DynamicZone too. Please describe your feature request The Component friendly name and icon is not enough if you have more then one instance from each type of component in the dzone list. As You can see the Title field value of Component is appearing on the DZone.Component AccordionToggle. Summary Extending the DZone AccordionToggle with Component.MainField value Why is it needed? Distingishingl DZone items without unfold all items. See: https://github.com/strapi/strapi/issues/12499