Prevent “px” from being added to numbers in custom css properties
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.
Non-developers should be able to make custom components on the Builder website builder
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...
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...
Preview URL should be able to take in a value, like an object mapping locales to the URL format
For instance, say one were to use the URL format of mysite.com/usa/en, this would mean that the site is localized to follow the format of /{country}/{language}. This means that for each page or section model, you have to duplicate your code of thi...
This could be useful for live feeds; similar to how socket.io works with websockets. It's actually a feature that DatoCMS has: https://www.datocms.com/docs/real-time-updates-api
Text type built-in Builder component should be able to accept a file as a link
If I were making a custom component, then I could create a prop that accepts a file as custom field. Similarly, I would like the built-in Builder text component to accept a file.
This one should be super simple to implement. Sometimes, we can get pretty long URLs with dynamic content. It'd be so nice to be able to see the entire URL at once, so could you PLEASE make the Link URL fields be textareas instead of inputs?
when a user has scheduled content they want to preview on a site or do some testing on, currently the only way to fetch the content from the content API is to manually include the date as a userAttribute: const targetDate = new Date();targetDate.s...
0
0
