Visual Editor

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

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

It would be incredibly useful to be able to discard all unpublished changes without having to enable live sync. Use Case: We are making changes to a page in staging, so we cannot enable live sync, since that would erase our published changes. And ...

Instead of offering choices to do different AI actions everytime I would like to have the ability to use the last one again. Ex: translating a field in a specific language

An option to force localization on some fields rather than toggling the option every time inside builder. When this option is selected, the field on editor appears as though a user is already opted for translation. Works similar to Localize option.

Builder has implemented the ability to switch between light/dark mode within the editor--awesome! What if we also had the ability to switch between light/dark mode for our content while editing it? So that we can test out different themes in our c...

Allow user to select which data model field value to display in a reference field, currently it only shows the record name

We would love to have our internal team review website updates through Builder.io's website preview links before publishing and have those comments appear directly inside Builder.io. This would be incredibly useful as we currently design things in...

Currently, Builder.io applies permissions at the content/model level, but lacks granular field-level control. Here's why field-level permissions are crucial: Sensitive Data Protection Different fields require different security levels: Pricing i...

Currently, Builder.io limits users to a single role, which creates significant workflow inefficiencies in real-world scenarios. Here's why multi-role support is essential: Many team members wear multiple hats and need different permissions based o...