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.

In an early Strapi v4 version (might have been v4.0), components inside dynamic zones were all expanded. A little later (might have been v4.4), components were displayed collapsed and content managers had to expand each component in order to see/edit the component. Now (v4.10), they are automatically expanded again. For content type structures that feature a lot of components, this makes the page very very long. It would be great if there was a setting which allows developers or content managers to configure if they want to display components automatically collapsed or expanded. Ideally there would be a system wide setting as well as a per-user setting.

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.

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.

When updating my plugins to support v5, I want to also export from the package a collection of types that can be used by developers/users of the plugin (things like the shape of the Config, shape of endpoint data, etc). Now that Strapi v5 has switched to using the exports map I wanted to add my types to this export map. "exports": { "./package.json": "./package.json", "./strapi-admin": { "types": "./dist/admin/src/index.d.ts", "source": "./admin/src/index.ts", "import": "./dist/admin/index.mjs", "require": "./dist/admin/index.js", "default": "./dist/admin/index.js" }, "./strapi-server": { "types": "./dist/server/src/index.d.ts", "source": "./server/src/index.ts", "import": "./dist/server/index.mjs", "require": "./dist/server/index.js", "default": "./dist/server/index.js" }, "./types/ ": "./dist-types/ .d.ts" // <--- Addition } After adding it, trying to build/watch with the @strapi/plugin-sdk (strapi-plugin build) I get the following error [ERROR] There seems to be an unexpected error, try again with --debug for more information ┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────┐│ ││ ValidationError: exports["./types/ "] must match the following: "/^\.\/. \.json$/" ││ at createError (C:\Projects\GESDev\ges-v2\packages\editorjs\strapi-plugin-react-editorjs\node_modules\y ││ up\lib\util\createValidation.js:54:21) ││ at C:\Projects\GESDev\ges-v2\packages\editorjs\strapi-plugin-react-editorjs\node_modules\yup\lib\util\c ││ reateValidation.js:72:107 ││ │└─────────────────────────────────────────────────────────────────────────────────────────────────────────────┘ I also tried to use the object form of an export entry, and got a similar error, indicating that it had to use the same format as the strapi-admin/strapi-server objects, which doesn't work in this case.

See https://github.com/strapi/strapi/issues/14627 When a new user for some reason clicks the confirmation-link a second time, an error message is shown on the backend, without any way to redirect the user to a more descriptive page on the frontend. -One solution would be to redirect the user to already configured login url with some extra parameter. -Or let the admin setup a separate url to go to after the confirmation-link failed. -Another might be to let the admin configure the url the confirmation-link goes to and then from that frontend page do a post to the backend and handle everything from there on out.

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.

Currently is impossible to open many entries by ctrl+click, on projects with a lot of data it becomes cumbersome to edit many entries one by one

If you configure your view, your changes are saved inside the database. Maybe we could save it like content-types in a json file so it can be shared between developers via git and enviroments.

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