All ideas

Most numeric custom css rules that we apply are `font-weight`, `order`, etc. We want a way to prevent the editor from adding the “px” suffix to these on every change.

I want to provide designers the ability to edit styles, but I also want to hide all the built-in components. Currently Components Only Mode always disables custom style.

Similar to how developers can create custom components, non-developers should also have this ability directly on Builder. Right now, non-developers can either: Create a template Convert template to symbol However, neither of these options actually...

In the advanced mode allow my templates to appear instead of the default templates. Allow for a default template for a given Model type. So that my users always get our "post" type already pre configured for them to start writing.

Hi, good morning First of all, congratulations for your work, I find it amazing, useful and powerful. The other day I discovered your AI plugin generate Figma designs. I am team leader of fronted project. I would love to be able to fit this plugin...

Although inheriting state by default can often make it difficult to debug in situations where there are modals, pop-ups, or web components being used, other customers would still find this beneficial and time-saving. Perhaps the option could be av...

If a customer wanted to change the significance attribution for A/B tests to 1 day (vs 30 day), they would be able to control that at either the account and/or entry level

Fsat landing pages imrove your conversion rate and as a result your paid media (FB and TikTok) results. We need to be able to create super fast landing page for paid media campaigns.

It would be great if there is a way to allow a UI designer to reference custom actions defined in state data to be passed to a custom component via a binding instead of having to use the custom code action editor. E.G. Using the multi-page funnel ...

When there is a plugin that uses a webhook like Algolia. If you change any part of the configuration, allow the user to see all of the webhooks that exist and delete any of the existing ones. Or place directions on how to access them within a model.