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

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.

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.

Allow uploading private files for Providers(S3, Google Cloud) which supports it. Allow sharing private files using signed url with expiry time. Add ACL support for files. Some kind of folder support. Currently we need to make S3 bucket public for reading. Also It will make media library more useful & it will add more security to uploaded files, currently a person who knows the URL can share it with anyone in unrestricted manner. so it can't be used for user's file which only user & some limited people can see & share.

Hi everyone! I think it would be very useful to have lifecycle hooks for Components, just as it is today for Collection Types. See: https://github.com/strapi/strapi/issues/15481

An addition to the existing Draft and Published states to round out the content lifecycle.

The data transfer feature is great ! We can enhance it to allow exporting to an external object storage in order to do backups easily and re-import it with another instance.

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

It's 2023, guys

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.