If you're currently using another solution to manage your content, you might be interested a lot in this feature. To make it short, it will allow you to import or export data directly from the interface (CSV, JSON).

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

TL;DR; Add support for specifying separate read-write and read-only database endpoint when configuring strapi instance. Details Modern web apps often deployed on cloud platforms like AWS or GCP or Azure. These platform offers very powerful Managed Database Services like RDS, Aurora (on AWS) or CloudSQL (Google cloud). These services are built to scale and offer separate database replicas for read and write operations to help distributing the load on the Database. Here: ( https://cloud.google.com/sql/docs/postgres/replication/create-replica ) and here ( https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ReadRepl.html ) Currently, Strapi only supports specifying a single DB endpoint that is used for all operations. This request is to add support for separate endpoints for write operations and one or many endpoints (could be round-robin balanced under the hood) for read-only operations.

Hi everyone! I think it would be very useful to have lifecycle hooks for Components, just as it is today for Collection Types.

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.

Actually is not possible to sort items that allows draft / publishing by publication date. Only by createdAt or updatedAt. It would be nice from the content mangager to be able to sort by publishedAt field! Cheers!

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

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

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