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.

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

Currently typescript compilation is a bottleneck when the app is trying to start, taking upto 16seconds in my case. The bun runtime promises and seems to provide faster startup times. We can provide a way to ignore typescript compilation when the runtime is bun. The current implementation looks for the presence of tsconfig.json to identify if the project is a typescript project and dynamically changes the outdir.

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.

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

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.

It's 2023, guys

It would be amazing if the image editor in the Media Library allowed for the selection of a focal point of the image so devs can crop responsive images accordingly. See for instance: https://docs.imgix.com/tutorials/focal-point-cropping

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.

Strapi added import/export feature in 4.6, 4.7 and 4.8. Unfortunately, it's only usable from command line, so if you can't connect to your Strapi instance through a terminal (I have a Strapi instance in Railway and cannot connect to it, for instance), the only way to backup your system is too use the 3rd party import export plugin which seems to be abandoned and will eventually stop working in a future Strapi update (currently, the whole database import is broken and you have to go collection by collection). It would be very handy having buttons to import and export the whole system in a single click, from the web UI. And if possible, it would be great if things like roles permissions or email templates were included in the export data.