Field Level Permissions - End User management
The current Users-permissions plugin is very limited in the control you have over accessing fields or even nested relations, components, and dynamic zones. Our intent is likely to replace the Users-Permissions plugin with an entirely new one, some information is available in the following issue: https://github.com/strapi/strapi/issues/2161
Add a "folder-like" group function to organize content types
I believe it would greatly improve the user experience if we can add a "folder-like" grouping function to content types (single type and collection type), so that if you have a lot of content types (for example if you have like 50 webpages, you will have like 50 single types), it really makes a lot more sense to have groups. For now users can only mitigate this by using some naming conventions, but I doubt if this is an elegant solution.
Customize the Admin Dashboard (Welcome Page) [v4]
In v3 you could override the admin dashboard as follows: https://forum.strapi.io/t/customize-the-dashboard-welcome-page/939/2 This no longer works in v4, or in other words no one in the community knows how to do this. The patch-package method is not a sustainable solution and not clean, I see that some people in the community would also like to know how to solve this in v4.
It might happens that you're going to develop a website which includes a blog. It could be interesting to split the APIs into two different projets. However, it can be annoyed to deploy on two different servers for such a little API. That's why the multi-tenancy is interesting! The multi-tenancy (or multi-projects) changes the architecture of an application to allow multiple projects in a single Strapi application. Each project is fully independent, you can use different databases, configurations, plugins, etc. More details https://github.com/strapi/strapi/issues/1465
Setting for collapsing/expanding components in the admin panel by default
In an early Strapi v4 version (might have been v4.0), components inside dynamic zones were all expanded. A little later (might have been v4.4), components were displayed collapsed and content managers had to expand each component in order to see/edit the component. Now (v4.10), they are automatically expanded again. For content type structures that feature a lot of components, this makes the page very very long. It would be great if there was a setting which allows developers or content managers to configure if they want to display components automatically collapsed or expanded. Ideally there would be a system wide setting as well as a per-user setting.
Allow nesting of components more than 2 levels deep in UI
I've recently read all the materials regarding the ban on creating deeply nested components. I saw that many people are asking to promote this feature within 3 years. I also saw that you removed the restriction for creating such structures in a raw schema. It seems to me that this is an incomplete solution to the community's request. In this regard, I have a proposal to add the ability to create such structures in the UI so that Strapi matches its stated capabilities to create any data structures easily, out of the box and without extra effort. Considering the fact that such structures may not be very efficient in terms of using dbms resources, I propose making the functionality disabled by default, but with the ability to enable it in the settings. Honestly, I don’t see any real objective system restrictions in order to allow editing such structures in the UI. From the outside it looks like 1 PR with a slight change in the layout of the entities module and 1 PR with remove restriction on the server side. Because I saw the Strapi rep's response regarding this proposal. The answer was something like this: “This feature is not in our plans yet” and we do not believe that it is advisable to include it in our plans entirely. I'd like to see a more expanded answer on this. Why do you think this functionality is not needed? What technical difficulties led you to this decision? Why did you unlock this functionality when editing the json schema, but did not unlock it in the UI? Why is there a depth limit of 2? Finally, I personally think this feature is critical. Because the existing limitation forces us to reinvent the wheel. So, what is your official advice to prevent creating deep nested components need?
Support for media folders in the content API
With the upcoming release of Strapi v4.3.0 and Media folders, the content API will not be able to utilize them. For those that believe it would be a good addition to also have folders at the content API level please leave a vote and comment what your use case would be.
HTML Customization for Admin panel Pages
It was great when we have more customization option in Strapi v3 for admin panel. The community is eagerly waiting for more customization options for admin panel HTML. Hope to have this in v4 or v5
Keep relations when switching between locales
When using i18n, it seems like relationships are dropped. When using translations, this can be a bit annoying.
Send custom messages from backend to admin panel
There should be the way to send custom messages in the form of alerts and toasts from custom backend code like from lifecycle hook to the admin panel. form example lets say i have implemented some logic using lifecycle hook after create and i am performing some task so when the task is done i want to send the message to the user in admin panel that the task is performed or some information about the task. After doing research and reading the docs i didn't find any feature similar to this. If there is already a way to do this then please tell me.