Add field grouping to core

+1 for adding Field Group to core. It's such a basic site builder tool, which the position as #10 most installed module → . It is enabled on ~44% of Drupal 8/9/10/11 sites (182,000/412,000).

Alternatively, 📌 Move Field Layout data model and API directly into \Drupal\Core\Entity\EntityDisplayBase Needs work could also solve this?

@ressa Field layout solves a different problem.
I agree field group should be in core, where it can be done much cleaner than in contrib.

The Ideas project is being deprecated. As discussed in a core committer meeting issues that are adding modules are being moved to the Drupal CMS project for discussion.

Field group is already included in Drupal CMS.

From a functional perspective, it is fine to have field group as part of Drupal CMS.

From an architectural perspective, the structure of entity form and view display should support grouping out of the box, so that field_group does not need the acrobatics that it currently does.

We should either reopen this and move to core queue, or create a follow-up issue.

@donquixote fair enough!

Totally agree with #44 still 16 years later :D Would simplify many things, not only frontend-wise, but especially in (entity) forms.

Probably to make it true it needs to resolve #1875974: Abstract 'component type' specific code out of EntityDisplay → and then even SDC elements can be used as wrappers

@andypost: That would be fabulous!

We just ran into an issue which is tightly coupled to the "parent" integration in core for fieldgroup, that needs to be partly solved in core for that reason to fix the major bug in field_group: 🐛 Field UI: Parent-child relationships not properly updated when fields are moved via drag-and-drop Active

With field_group in core we wouldn't have such logical problems. (Maybe you could have a look at the blocking core part @andypost?)

Thank you!