Quick review after testing this early rework:

• first of all: great job, it's much cleaner.
• Applied attributes (full width, mandatory, etc) in the preview panel are not done for custom fields.
• move the mandatory attribute after the label (like displayed in the final form), same for all other attribute icons like read-only
• grip icons should have a grab pointer
• Maybe, we can reduce a bit the contrast of the line between drag control and label
• "New field" button should have a hover state
• Search input doesn't work.
• a suggestion (where I take opinion), maybe we should have at creation only a subset of native fields already placed in the preview panel. [Name, serial, manufacturer, Model] could be a good start. The idea behind this is to improve the discovery of how the right panel works. If all fields are directly in place, the right panel is empty and we don't understand clearly its purpose.

Quick addition:

• Maybe we can make the fields a bit contrasted. I applied gray-100 and a transparent border to the fields.

While discussing drag controls, in fact, let's remove them completely:

• add a grab cursor on the whole div of the fields
• The discoverability of dragging (hover not available) in responsive view is not that important for admin features.
• I think we still need a way to edit a field in responsive mode. Not sure about the best way. To avoid default/selected states (because of complexity), I suggest to keep hovering on the desktop view but always displaying controls on responsive.

Moar:

• If any attribute is applied, like read-only, on my side, fields will always be displayed as full-width. Either this attribute is set or not. Moreover, if I remove all attributes, it keeps the full-width display.
• For "New field" button, could you add btn btn-sm btn-ghost-secondary w-100 classes? The current hover style is not sufficient.

a suggestion (where I take opinion), maybe we should have at creation only a subset of native fields already placed in the preview panel. [Name, serial, manufacturer, Model] could be a good start. The idea behind this is to improve the discovery of how the right panel works. If all fields are directly in place, the right panel is empty and we don't understand clearly its purpose.

I think users will expect all of the native fields to be present already, especially if they are fields related to capacities they enabled. Also, if they are creating multiple custom asset types they may get annoyed if they have to keep enabling all of the native fields. This may be a place where a discovery tutorial could be useful, or just try to have an intuitive UI. I find the sidebar design intuitive as it is (maybe hide the section headers when they are empty), but I don't know how other people will see it.

• A last bug, after saving and reloading, attributes are not applied on fields. A edit and save for a field temporary fix the issue

I think users will expect all of the native fields to be present already

ok.

maybe hide the section headers when they are empty

I would like to see how it renders

maybe hide the section headers when they are empty

Ok for the current state. I guess we should always keep "custom fields" section because the button for adding will always be present.

Apart this, PR is ok for me, please fix tests, and we will go for merge.

Remaining test failure doesn't seem related at all.