Feature Requests

Hi, I was searching and looking at the plugin @strapi/provider-upload-cloudinary to replicate the folder structure (folder_path) to replicate the same structure on the Cloudinary side. Perhaps someone else already requested a similar feature/improvement but I believe this is a quality-of-life improvement for all developers using Stripe. I've seen a lot of effort from the Strapi's team lately with v5, and I want to help (if possible) to make Strapi a better product for the future. Cheers.

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 my project, the content editors are often writing their content in a tool of their choice, such as Notion or Google Docs. Currently, rich text formatting from tools like Google Docs is stripped, and the content is pasted as plain text. Between Google Docs & Notion, copy-pasting automagically preserves basic formatting in both ways. I'm not sure how it works, but it would be nice to have this convenience in Strapi too. Notion generally pastes into plain text fields as Markdown, also in the Blocks Editor, but that Markdown isn't auto-converted to its blocks editor equivalents.

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.

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.

It would be great to have an option that trims text by removing unnecessary whitespace characters around it. For example, cases like this should be cleaned up: <br/> ...content... <br/> <br/> ...content... <br/> ...content... <br/> I get that in some situations, extra spaces or line breaks might be needed. But in most cases, they break the layout and end up displaying empty blocks on the page. The issue often comes down to editors (people) accidentally leaving empty lines and hitting publish. It’s hard to catch these changes manually, and implementing serialization logic to handle this is tricky, bug-prone, and inefficient performance-wise. BTW: @strapi/blocks-react-renderer adds a <br> tag by default even if the input field is empty!

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

Ability to duplicate a component in the dynamic zone including the content

It would be great to have a native feature in Strapi that allows developers to translate the admin interface into different languages, such as Spanish. The feature could include: An option to select the desired language directly from the settings. A translation editor within the admin panel for customizing language strings. Support for community-contributed language packs to encourage collaboration. This would make Strapi more inclusive and accessible for non-English-speaking users and projects operating in various regions.