All ideas

As mentioned on the forum, https://forum.builder.io/t/svelte-sdk-need-a-little-love-now-svelte-5-is-here/6904, Svelte 5 is here and taking off fast. There have been several updates already to Svelte and Sveltekit. I'm running into an issue with th...

When creating content, it’s essential to present information to the Content Editor in the most organized way possible. Currently, in the left-hand menu (the "Insert Menu"), you can freely order the categories that you register as part of the code....

When using list inputs (while registering a custom component) we should be able to define minimum and maximum amounts of items that can be added to lists to prevent publishing blocks that have too many items or too few items (i.e. can only have be...

After selecting an optional enum value from the dropdown list in the custom component options you’re unable to remove the selection afterwards. The only way to clear it is to delete the component and recreate the entire thing.

We've noticed an issue with how design tokens work between spaces. We have semantic design tokens, like "Brand Primary 1" and "Brand Primary 2" which connect to a css variable, such as --primary-1 and --primary-2. We have multiple sites, which sha...

Within the Assets library, there is no way to see which assets are currently in use, or on which pages. This would: Enable a check when deleting assets that are currently in use Help organizations/users cull unused assets, for when their quota is ...

It would be great in the Content API, to be able to get the total amount of items in the return of the getAll method. That would allow us to be able to display a very common pagination pattern with numbered pages. At the moment, we do not know if ...

Currently there is no good way to allow defining a visible but non-editable input type. Possible usecases for this would be Custom Code function to enable/disable editing of the input field (possible role-based editing for select fields of a custo...

I think having a color field as the setting of environments and displaying it consistently as a small top bar or something else could really help avoiding human mistakes. It eliminates a mental load of being constantly aware of which env I am in a...

Allow list of references to use field from referenced content as a label. We have a long list of possible api errors Currently when viewing the list all you see it 'api-error 1', 'api-error 2', etc It would be nice if instead we could select a fie...