All ideas

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

For more complex layouts, CSS Grid is a necessity. Unfortunately, Builder's Visual Editor has no real support for CSS Grid, other than doing everything through pure CSS, which isn't really approachable for many less technical folks. It'd be really...

Currently uiBlocks input type accepts any type of built in and custom components from Builder. I would like it to work the same way as childRequirements for custom components with children where you can define list of components that can be used. ...

We want to fire a web hook whenever an admin user “Requests to publish” content so that we can build a slack integration to notify the users tagged that a page is ready for review.

We have a React Native SDK in beta, so would be great to also have a Flutter SDK as well

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

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

Right now it's impossible to add a one-off global data model. An example where this could be useful is something like a highlight article. You could create a model that references an article. This model should only have one entry. Right now you co...

You should be able to easiliy query data based on it's presence in a folder. This would be very handy for using data in query on the page builder. For example, if I am showing a leadership page that displays the list of company leaders it would be...

It would be useful to be able to hide a set of fields based on the content of another field within models defined through builder's dashboard. This is possible with custom components by writing some code, but not for fields defined in the dashboar...