All ideas

When defining inputs for models, it can get overwhelming to manage a long list of individual inputs—especially when multiple inputs are related to the same section of the model. For example, if you're building a hero section, you might define inpu...

Currently when adding a new user to multiple spaces the users role within those spaces defaults to Designer. An option to select a user role when adding them to multiple spaces would be very helpful so that an admin doesn't have to enter each spac...

there are some runtime errors that are picked up while app is running and the try fix button cant pickup all at once, by using the button "try fix" which is provided by builder.io when app run into the error, it's more costing, this was free on th...

Currently it only tracks custom components that are being used, would be great to track builder-provided components as well

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

I would like to be able to target on a component level instead of on a page level. This would give a lot more flexibility without having to maintain two, almost identical, pages. For example, if we apply translation for most of a page, but a speci...

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

Can a feature to be developed to allow a default tenant to be determined for a multi-tenanted system.

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