All ideas

Provide audit logging for a space similar to what contentstack does as described here: https://www.contentstack.com/docs/developers/set-up-stack/monitor-stack-activities-in-audit-log

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...

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...

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...

You have to be kidding me. Stop making people pay for support. Just stop doing it.

When building locally and on a deployed server using Vercel I am finding that the biggest thing that is slowing me down and causing inconsistencies to my workflow at the moment is caching. Vercel caches heavily so updates on Builder take a while t...

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...

When building dynamic Symbols with many Content Inputs, I find that I often have a need to copy a previous Content Input and just change the name. It'd be really nice if I didn't have to go into the JSON Editor to do that and could just click a bu...

For the purpose of restricting certain fields in a data model from being edited by any user, I should be able to target the current user's role in a validation hook. Something like async function run ( ) { if (context.user.role != 'admin' ) { retu...