Content Editing XP

I would need a way to set alternativeTexts per language on files in the upload plugin. For now I just built a custom collection, which contains a file and localized alt text. However, I think this is a very common use case and related to i18n plugin, so I just opened as an issue. See: https://github.com/strapi/strapi/issues/10220

Add i18n options for content manager view settings (eg label, description, placeholder) See: https://github.com/strapi/strapi/issues/10110

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

Currently a validation error if a field has a regex pattern validation simply states "Value does not match the the required pattern". This leaves editors clueless about what needs to change in order to fulfill the validation requirements. Strapi should display the required pattern as part of the error at least.

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

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

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.

Will a normal search engine be added in the future for fields with relation. Capitalizing word for word every time is not very convenient, but I would like to type only keywords as with normal search engines. I would also like to extend the drop-down list, if there is enough data, 2 lines are also not very good.

We want to enhance the CMS homepage with additional widgets to provide more useful insights at a glance. Currently, the homepage includes two widgets: one displaying the last edited entries and another showing the last published entries. We will introduce an API for the homepage that will allow users to create their own widgets and fully customize their CMS homepage. Every user has different needs, and with this API, you’ll have the flexibility to design a homepage that works best for you. Whether you need more visibility on project statistics, editorial workflows, or external integrations, you will be able to tailor your CMS homepage accordingly. We will also introduce new default widgets to improve visibility and efficiency for Community and Paid Edition users. For the Community Edition: User Profile Widget: A dedicated space for user details. Project Statistics Widget: Overview of key project metrics (Number of entries, assets, content types, components, admins, API tokens, webhooks, locales) Entries Overview Widget: Quick summary of content status (Number of draft entries, modified entries, and published entries) For the Paid Edition: Assigned Entries Widget: Displays entries assigned to the user when the Review Workflows feature is enabled. Upcoming Releases Widget: Highlights upcoming releases for better planning. Audit Logs Widget: Provides quick access to recent audit logs.

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