Share your feedback...
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.
Responsive Administration Panel
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.
Q1, 2024 — Draft & Publish
Allow users to manage content by having a published and draft content at the same time.
Allow setting the global default preferedLanguage off of "en"
When you want to enforce a different default language for new users to something other than english there is currently no way to set this (eg via the app.js) and say set the forced default to "fr". Suggested by a community user on Discord.
Q2, 2024 - Content history
Track version history of content: view the different iterations of a piece of content.
Content editor lock
Currently there is no content editing lock. This can result in issues when 2 editors are working on the same content. In example editor 1 has saved some changes, while editor 2 has the same (old) content already opened. Editor 2 saves his changes after editor 1, and the changes from editor 1 are lost. Realtime editing with multiple editors would of course be the future, but in the meantime I would suggest a lock on the content, similar like in the WordPress CMS.
UID field is always localized
The UID field is always localized. This does not always make sense. A unique ID might need to point to a unique resource where the localization is irrelevant. For example, you might use the UID field to create a slug for a page. Some websites localize their URLs (e.g. /about and /over) but another common pattern is to prefix the path and use the same slug (i.e. /about and /nl/about). Another issue arises when the localized fields are the same (e.g. /book-reviews/harry-potter) where you would get /book-reviews/harry-potter and /book-reviews/harry-potter-1. Please consider making the UID field localization setting customizable. See: https://github.com/strapi/strapi/issues/15248
i18n for media alternativeText
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