Provide some generic components

It was included in another (alpha3) issue MR, wasn't it?

See the updated content of this issue, 2 of them were included in other mr.

oh yes, the issue description was updated. My bad.

Hello,

I don't think it is up to the display builder tool to provide the components. The components will be provided by the design system used on a website.

Otherwise we will end up like with the 4 Core layouts (1, 2, 3, 4 columns) that we (I only?) use in BO dashboards and that we have to remove with stuff like Layout Builder Restrictions in front.

Special case for "HTML Element": I have something similar on projects, and having something like that would definitively become handy to not have to duplicate it on every projects. But let's put it in UI Patterns 2, why only reserved for Display Builder users?

Discussed with @mogtofu33 during weekly meeting.

HTML wrapper and HTML void element components to go into UIP2

Grid/Flex/Space, to precise, either:
- submodule labelled as demo (problem of Composer namespace)
- test module
- separated drupal.org project (but risk that other people propose their own stuff)
- document as best practice, like the grid_row component was identified as a best practice in its time.

To avoid confusion with components provided by Design Sytems, maybe we can:

• mark them as noUi to not show them in the ComponentLibrary
• display them in the BlockLibrary under the "Element" group

Mark them as noUi is planned when we are Drupal >11.3

Block? I don't think it's a good place, code of this island is already too complex.

We can add something to the label or have an other group than Layout.