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.

When using a Multiple Image field in the content editor, the thumbnails are extremely small in the horizontal gallery view. This makes it difficult to identify images when working with large collections. Is there a way to increase the size of these thumbnails or change the display to a more usable grid layout? Additionally, it would be very helpful to have an image preview appear when clicking on a thumbnail in this view. I've attached a screenshot showing how the thumbnails appear. As you can see, they're too small to be useful when managing many images.

I'd like to request a feature that allows custom fields to block collection saving if their validation fails. Use case: I've created a custom field which is a text input. Its validation depends on the value of another select field. I use a regex inside the custom input component to validate the value, and display an error using <Field.Error />. Currently, even when the input is visibly invalid, Strapi still allows the collection to be saved with the wrong value. This defeats the purpose of custom validation. What I need: I would like the ability to prevent saving a collection entry when a custom field is invalid. This could be done by supporting a new prop in the custom field component, for example: ```const Input = forwardRef( ({ attribute, name, onChange, value, validationError }: InputProps, ref) => {``` Where validationError could be: ```{ isSaveBlocker: boolean; errorMessage: string; }``` Expected behavior: If validationError.isSaveBlocker is true, the admin panel should prevent the user from saving the entry. Optionally, the errorMessage can be shown in a global or contextual warning to explain the issue.

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.

It would be great if we can version of our apis. v1/posts v2/posts

The review workflow allows to set assignees for individual content entries. However there is no way to see all the items that are assigned to me. It would be great if we can add a filter or a more intuitive way to check all the entries that are assigned to me. Also if we can add the ability to filter by review stage that would be great

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

Making the theme accessible as CSS variables would help developers use more native CSS like syntax when writing their styles. It wouldn't be too hard to implement we could add a style tag to App.tsx and set its HTML to the theme object transformed. Here's a super quick demo I threw together https://codepen.io/Link2Twenty/pen/dPPXXQv?editors=0110

At the moment, if someone add the color-picker custom field to a collection/component, the picked color is shown in the collection list only as a Hexadecimal string. It would be really nice if it could also show the actual color, like in the edit/create view.

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.