All ideas

Query filters are great, but let's be honest, if someone builds the user facing functionality, it usually means the search bar need to be as "smart" as possible. Having the ability to filter the content in a fuzzy way would imo add a lot of value

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

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

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

Do you have any plans to support light boxes on pages? This is something that would be helpful when designing landing pages.

I feel like the side panel is a poor place to put Options/Fields. There are some scenarios where I have deeply nested fields (see attachment). The UI becomes progressively more difficult to use since the real estate for fields shrinks. Two solutio...

In older versions of builder the toolbar always dispayed. It's now auto-hiding when the mouse is not hovering. This class in particular (.hide-until-toolbar-hover) causes it. The Issue: When you're developing locally, at a quick glance it becomes ...