All ideas

Right now assets can only be categorized in the Asset Library in Production (Main). We stage all of our content on a Staging branches, so it's more work to go to production to categorize assets and then go back into Staging to use the assets

Love Builder but the inability to sort content by primary headers (Name, Target, Link Status, Updated, etc.) is sorely lacking. Please consider implementing.

Ability to hide/remove sub-text/sub-heading(value of design token) from design token list item in visual editor

Have the ability to add additional breakpoints. So just rather than the three default, have the ability to add an additional one if needed

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