All ideas

When using list inputs (while registering a custom component) we should be able to define minimum and maximum amounts of items that can be added to lists to prevent publishing blocks that have too many items or too few items (i.e. can only have be...

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

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

Similar to how if you were to use AWS S3, the same URL can be used for when new versions of the file are added, so it's always kept up to date. Currently, in Builder's asset manager, you can't simply replace assets, like images. You have to upload...

Allow list of references to use field from referenced content as a label. We have a long list of possible api errors Currently when viewing the list all you see it 'api-error 1', 'api-error 2', etc It would be nice if instead we could select a fie...

We've noticed an issue with how design tokens work between spaces. We have semantic design tokens, like "Brand Primary 1" and "Brand Primary 2" which connect to a css variable, such as --primary-1 and --primary-2. We have multiple sites, which sha...

Currently localization of blocks can happen on an individual input level within the block (see attached screenshot), this leaves room for error where a user may input localization for some inputs in a block but not others (i.e. a banner heading in...

Currently styles are inherited from the desktop view. Some designers prefer to start building with a mobile view first so it would be nice to have the option for style inheritance to go the reverse direction - tablet and desktop inheriting from mo...

Love the editable breakpoints. We'd love to add in a 4th breakpoint, "large desktops" to work in. I could see someone only wanting 2 breakpoints, mobile/desktop as well, so might as well make it all configurable. Thanks!