All ideas

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

For better content organization, I suggest adding internal tagging. That’s an efficient way to group all types of content (page, data model, section, etc.) that are related arbitrarily. Say you are running a sale event which needs 5 new pages 15 s...

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

While lazy loading is in general a good thing, you often want to load the first contentful paint normally. To avoid having to write JS to achieve this, this could be done with a simple checkbox option labelled "Lazy Load" in the Block Options for ...

Right now the asset library only allows you to find assets by the asset name and one level of folders. If you have alot of images (say 1000+) it can be very hard for users to find the image they are looking for. Having the ability to tag images or...

Right now, when creating a new custom component and registering it with Builder, the field "Link URL" will always show up in the editor, allowing content editors to wrap the whole component in a link to an arbitrary URL. It's possible to disable t...

As of now, Live Sync is enabled for main->{environment} by default for models and content. It would be great to have the ability to turn this off by default; that is, a main environment would not push to child environments AND there would be no...