Have the ability to localize everything directly on Builder
I love how easy it is to localize text directly on Builder, but for everything else, you have to either create a data model or localize the entire page. Would be nice to just localize an image (or any of the other basic, built-in Builder component...
When working with Symbols, we like to use logic to allow a field to be overridden if populated but provide a secondary fallback if the value is nullish. Unfortunately, if you just empty the text in an input right now, it leaves it as an empty stri...
It would be great to add multiple choice in enums of text field or create a separate built-in field type. Also addig multiple references in Reference field type would be great.
Currently you can support standard non typed versions of defineProps, such as defineProps(['prop1', 'prop2']) <-- supported in builder sdk in typescript, you would define them as defineProps<{ prop1: string, prop2: number }>() <-- not ...
This is mainly a nice-to-have feature, but one minor annoyance of the visual editor is that it will autofill 'px' even when I don't want to use pixels. You are able to override this with your own value, but this gets repetitive. Our team has certa...
With increasing amount of custom components its inefficient to search through grid view for the custom component of choice. It gets even worse when the list isn't sorted by leading character. -> As a Marketeer, Developer, Designer I like to fin...
Allow aggregation operations: $cond, $ifNull, etc.
I want to query content items using the query syntax but manipulate the set of returned items based on certain conditions. My main use case is that I want to query for a URL path and a custom targeting attribute. If there's a content item for that...
0
1
0
