Hi Thiago! Thanks for working on this!
I really like the new designs. My only feedback would be that, as Adina stated in point 5 of her proposal, I think there should be multiple types of fields depending on the expected data.
For example, in the case of CSS Class, it would be fine to keep using a text field.
However, for content where we already know the expected values, for example the Image field, where we already know the images available on the page, I think the field should become a dropdown with the available items.
Same for other config options where we already know the values.
e.g.: The livedata macro has the layouts option that only takes table and cards as values. At the moment you need to input the words manually in a text field. I think it would be better to present the user with a dropdown from which they can choose either of the 2 available options.
Agreed. I’d also add an indicator to let users know those fields are required. A simple * would suffice in my opinion.