Feature Requests

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.

The graphql api can return an image in different formats (sizes), but the UI lacks this functionality and we can only copy the image in the original size. This is useful because sometimes we just copy / paste urls in our frontends instead of getting that data from the API.

I need custom validation error messages for the backend that would look like content-type.validation.field.error-type . But I found it is very cumbersome to implement without doing a lot of additional things like overriding lifecycles, adding graphql middlewares etc. `{ "errors": [ { "message": "This attribute must be unique", "path": [ "createMarketingLead" ], "extensions": { "code": "BAD_USER_INPUT", "error": { "name": "ValidationError", "message": "This attribute must be unique", "details": { "errors": [ { "path": [ "email" ], "message": "This attribute must be unique", "name": "ValidationError", "value": "aa@aas.aa" } ] } } } } ], "data": { "createMarketingLead": null } }` Instead of "This attribute must be unique", it could be a marketing-lead.validation.email .required, which in turn allows for end users to hold the i18n strings. ### Why is it needed? The messages are currently in unorganized format. A central coding mechanism would be great addition to the framework and organize error handling structurally.

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

Please extend the conditionals behavior. The idea of adding conditionals is great, but the way they are working now is really shit. Fields that are conditional and become hidden are not cleared so other fields relying on these fields are still shown. Then only 1 condition is not enough, we should be able to combine conditions as well.

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!

it would very nice to have the strapi import/export cli as lib. i want to use db migration for first initial db. its already working in cli, just export it as library...

Currently, when a custom field is added to a content type with visible: false, the field is hidden from the Content Manager UI and cannot be edited or updated through the admin panel. This also prevents updating the field using the onChange function inside a custom widget or Edit View panel. As a result, it is not possible to programmatically set or update the value of such fields from the admin interface, even though they exist in the schema. It would be very helpful to have the ability to interact with and update these hidden fields programmatically (e.g., via custom widgets or panels), even when they are not visible in the default Content Manager UI. This would enable more advanced use cases and custom workflows.

is it possible to have a separate active and passive databases with same data synced in between? Active database - to be used by the primary website with huge traffic Passive database - to be used for APIs and 3rd party uses