Supporting entity form displays

Thanks for creating this issue!

Do you mean entity form displays (for e.g. article nodes), or do you mean the fields + field widgets used to populate the props of an SDC?

The idea is to manage it on the level of fields (with their available widgets). Similar like you can use Layout Builder instead of the Manage Display configuration page, i.e. the configuration page of Manage Form Display would be replaced by Experience Builder for arranging the fields and configuring their widgets.

I mentioned the example of the Field Group module. The site builder may instead create such field groups within the Experience Builder, and placing configured field widgets into such a group.

Such thing immediately brings up the question of "why re-inventing the wheel" but I think it's a necessary thought when we want a more consistent UX for the site builder.

@lauriii's vision for Experience Builder so far has been that all that should be necessary, is defining an SDC and the shapes of the props it has.

IOW: no need to configure field widgets. In fact, that's what we had originally in ✨ Allow specifying default props values when opting an SDC in for XB Fixed , and which @lauriii very explicitly asked us to move away from, which we've been doing in 📌 Support complex SDC prop shapes: introduce (Storable)PropShape to compute field type storage settings Fixed and is continuing in subsequent issues 📌 Auto-create/update Component config entities for all discovered SDCs that meet XB's minimum criteria Fixed and 📌 [PP-2] Remove Component config entity's add/edit form Postponed .

I do see where you're coming from though: What if the form UX is not good enough? — that's fair! XB is currently literally generating forms using existing field widgets for the SDC props in the order that the SDC lists those props. So I suspect this will be a future problem/question we'll need to address.

Requesting feedback from @lauriii to ensure I didn't misrepresent what he's told me.

P.S.: Acquia's Site Studio product has something like this in the "Form Builder" part of Site Studio.

If I'm reading this correctly, @mxh is asking about the entity form displays for the host entity itself. If this is true, this is not related to how the forms for individual components get generated. What I believe is that the form display of a component should be managed by the author of that component. This means that if the component is authored in code, the form display is managed in code. If the component is authored via UI, then the form display too is managed via UI.

I believe that XB will continue to have a concept of being able to customize the form displayed for the host entity fields. We haven't designed this experience fully so I don't have any visuals to show how this would work. I will post screenshots here when this has been designed and/or when we know how XB impacts the host entities form display.