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

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.

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).

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

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

see: https://github.com/strapi/strapi/issues/8692 see: https://github.com/strapi/strapi/issues/12188

It would be great if we can version of our apis. v1/posts v2/posts

Update Strapi React dependencies to React 18!

Would be great for authors, if they could copy and paste components between content type items. E.g. if a content type represents pages, an editor could duplicate components from one page's dynamic zone into another dynamic zone.