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's 2023, guys

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.

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

If a webhook update content - we will get into a loop. Instead add the ability to know who triggered the webhook by adding a headers - for example - is it a REST call or a user from the UI who trigger that webhook

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.

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

As a Strapi admin and content lead, I want to export audit log data to CSV/Excel for filtering and sharing in team reports on documentation updates.

### Describe the request Currently, when sorting entries by a nullable field in Strapi, null values are placed at the end when sorting in ascending order and at the beginning when sorting in descending order. This behavior is consistent with common database sorting practices. However, there are use cases where it would be beneficial to have all null values sorted at the end, regardless of the sorting order (ascending or descending). ### Proposed solution I propose adding a configuration option in Strapi to control the sorting behavior of null values. This would allow developers to specify whether null values should always be sorted last, providing greater flexibility to accommodate different use cases. ### Alternatives considered An alternative could be to handle this at the application level, manually reordering the results after they are returned from Strapi. However, this would be less efficient and more complex than having the option built into Strapi itself. --- This feature request is an extension of the discussion in Issue #12593 . It was noted that Knex.js added a means to control if nulls are first or last, but this feature does not appear to be exposed in Strapi. Exposing this feature in Strapi would provide developers with more control over their data sorting behavior.