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 inclusion of both text and image content on a webpage is essential, and having the ability to preview images directly within the Rich Text (Blocks) editor would certainly enhance the user experience. However, it seems that the current version of Strapi (v5.0.3) does not yet support this functionality in the Rich Text (Blocks) editor, as indicated by the available documentation. Currently, there is no option to insert images directly in the Rich Text (Blocks) editor, even if an Image URL from the assets library is provided, it renders as a normal link. It would be greatly beneficial to have an image management button that facilitates image handling within the Rich Text (Blocks) and allows for real-time rendering of images.

I propose adding a hover effect to highlight sponsor names on the welcome page. Clicking the name will also direct users to the sponsor's website, improving both interaction and functionality. I attached the screenshot of this .

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.

Summary Currently the SSO implementation is entirely gated behind the SSO gold plan. This makes sense for enterprise customers that do not wish to spend extra effort implementing it. For those of us with shallower pockets, one would hope that it'd be possible to write your own plugin / implementation. Currently due to the fact that it's impossible to override the admin backend (without forking), there is no feasible way to enable alternative auth strategies as passport is initialized with a localStrategy only. For this reason, I ask that the Passport strategies are configurable outside of the EE Gold plan. Why is it needed? I'm frustrated that the extensibility of the auth system is only reserved for EE Gold plan. Suggested solution(s) I ask that the Passport strategies are configurable outside of the EE Gold plan. See: https://github.com/strapi/strapi/issues/11409

I'm using Strapi to create scientific documentation website with deeply nested, interlinked section content structures. Multiple editors with no coding background work on the website's content, making the Rich Text editor ideal for their needs. Currently, there's no straightforward way for users to set internal links to open in the same tab. I propose adding an option in the Rich Text editor to allow users to choose whether a link should open in a new tab or the same tab when creating or editing links.

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.

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

It was great when we have more customization option in Strapi v3 for admin panel. The community is eagerly waiting for more customization options for admin panel HTML. Hope to have this in v4 or v5

Description: As a developer, I would like the disconnect and connect arrays in the events params data of Strapi API requests to show whether there is a connected relationship between the updated content type and other content types, even if the relationship hasn't been updated. This would allow me to detect when a relationship exists and take appropriate action. Details: Name: hasRelation Type: Boolean Default value: false Location: This parameter should be added to the disconnect and connect arrays in the events params data of Strapi API requests that update content from a content type that has a connected relationship with other content types. Behavior: When a request is made to update/create content from a content type that has a connected relationship, the disconnect and connect arrays in the events params data should include the hasRelation parameter. If there is a connected relationship, the parameter value should be true. Otherwise, it should be false. Use case: This feature would be useful for scenarios where it is important to know whether a relationship exists or not, even when the relationship hasn't been updated. For example, a developer may want to perform a certain action only if a relationship exists between two content types, or may want to display a message to the user indicating that a relationship exists. Implementation: This feature can be implemented by modifying the code that generates the events params data for Strapi API requests. Specifically, the code would need to be updated to check whether there is a connected relationship between the updated content type and other content types, and then include the hasRelation parameter in the disconnect and connect arrays with the appropriate value. Impact: Adding this feature should not have a significant impact on the performance of Strapi API requests, as the check for connected relationships can be performed efficiently. However, it may increase the size of the events params data slightly, depending on the size of the content type and the number of connected relationships.