Builder for Developers

When fetching content entries using SDK or API, the scheduled content is also returned with the published flag having a value of published. It will be great if we have a new flag scheduled=true or the published flag has a value of scheduled , or s...

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

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

Instead of having to setup custom events and conversions separately, it'd be great to be able to integrate existing GA4 profiles to pull in custom events, conversions and more information into the insights and use that information for A/B tests. T...

Builder should be able to automatically generate typescript defintions for model. This would greatly increase the DX when using Builder, and could probably done pretty easy. I dont have any code examples currently, but for brevity a builder.get("e...

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

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

Right now, when creating a new custom component and registering it with Builder, the field "Link URL" will always show up in the editor, allowing content editors to wrap the whole component in a link to an arbitrary URL. It's possible to disable t...

As of now, Live Sync is enabled for main->{environment} by default for models and content. It would be great to have the ability to turn this off by default; that is, a main environment would not push to child environments AND there would be no...