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
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.
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.
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.
Webhook by content type
I have some content types that should not trigger a webhook (Gatsby Build). It would be great if I could checkbox per content type when the webhook should fire.
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.
Export schema changes to SQL
Hi, Our dev team has concerns about deploying new versions of Strapi that might potentially change the our production database schema in unexpected ways. It would be great if we could export the database changes as a SQL file while running locally, so we could turn off automatic migrations in production and just run the SQL files instead. This feature request here https://feedback.strapi.io/feature-requests/p/disable-migrations-option is related. Thanks, Jamie
Allow customization of foreign keys for options like cascade delete