Ideas

We have created our own custom button component so that we do not ever want to use the basic button component, but we do use the column component sowe do not want to hide all basic components and styles, just the ones we never want to use

When working with Map custom inputs, either in Symbols or in Content Models, the default input box is a simple input field. This would probably be fine if the majority of editing on these fields didn't happen in the narrow sidebar, but because tha...

Users frequently apply h1, h2, etc heading in their content, thereby breaking SEO by creating duplicate headings on the page. No amount of training or explanation removes this risk. Ideally, admins would be able to completely remove the option for...

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

currently i cannot see a way to delete an entire model. i should be able to delete it if i want. there is also no easy way to delete entires. the only way i can see, is to open each entry individually and delete it - which is too time-consuming

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

(Please see attached file) That left side panel area where all the custom fields are... I hovered over the vertical scrollbar as well as the black editor json windows, but there wasn't an option to increase the width of those sections. A request I...

check in code generated by builder io to github

A customer wants to use Smartling to translate content; at the moment, the only way to archive this is by publishing the content. As you can see in the point 1. https://www.builder.io/c/docs/integrating-smartling#translating-with-smartling-in-buil...

If you are injecting a file (in my case, an image) into a custom component, all that seems to be available (via GraphQL) is the file URL. It would be really useful to be able to access more file information, for example, natural width and height. ...