All ideas

You can use ref.ref inside content JS when using the React SDK to reference the DOM element for the content item, but this feature isn't provided for the other SDKs. This is a very useful feature when you want to manipulate the DOM for just the co...

You can use ref.onStateChange inside content JS when using the React SDK, but this feature isn't provided for the other SDKs. This is an important feature when using content JS inside of complex symbols. For cross-compatibility and functionality, ...

This could be a dealbreaker for us, since we have teams all over the world. Builder is nearly perfect other than this!

Right now, we are not able to create versions for data model like we are able to create for page model. So it will be a good feature if we can implement this.

I understand sometimes you want different user permissions for different environments, but some teams actually want the same permissions across environments, and it can be a pain to have to add and update users in multipl places. Would be great if...

Hello team, with requiremnt going more personalized and category specific for ecommerce, search/ product detail page requires to show differently when given context of category or personalization of segement. I would like to see how can we create ...

We have gotten errors when trying to publish pages due to "size of the page/content". However we currently have no way to see the size of each block to know what is bogging down the page.

It is possible to have enum for values, but this makes it mandatory to use enum values. It would be awesome to have suggestions, like "most used values". Example: I have an AspectRatio component. I allow all numbers, but I would like to have most ...

Number input needs only pure numbers. It would be awesome to allow calculable values. Example: I have the AspectRatio component. 16/9 is 1.77778... which is kinda hard to remember.

Currently when you add a model type as a field for a model the model you are working with is omitted from the drop down. It would be nice for a model to be able to include itself so that we can build recursive models. e.g. SomeModel { field1: stri...