[Suggestion] Switch from Display Suite to Layout Builder

Thank you, Anietie for suggesting.

Having the following on the table for quite some time

[Proposal] Remove Display Suite module from Varbase 10.0.x in favor of Layout Builder and UI Patterns

This is the answer to follow with Components, UI Patterns, Layout Builder and Storybook

No DS, No VMI.

I had people testing this for 5 weeks.
It is not easy but it is the logical move in my opinion
Only Layout Builder with UI Patterns to slate Components
This way all work will be in coherence
Layout-able modules and layout-able layouts for sections

Default components were built and implemented in our theme.
UI Patterns will work to stack components into other new components from the UI
Layout Builder will help to stack components in default layouts stacked in sections

No need for DS anymore if we are moving to Components
It will be a distraction to the workflow

• Blocks should not use DS ( which we agree on - Implemented)
• Content Types should not use DS ( which we agree on - NOT implemented yet )
• Terms should not use DS
• User Account entity types should not use DS
• Custom entity types should not use DS

Looks like a great path forward

Manage display 3.0.0 stable was released on: 23 May 2023 by: AdamPS →
https://www.drupal.org/project/manage_display/releases/3.0.0 →

This project makes base fields such as 'title' available in "Manage Display".

This very simple module uses the framework that is already in Core rather than inventing anything new. The goal is that most or all of this module will be absorbed into core
#2353867: [META] Expose Title and other base fields in Manage Display. ✨ [META] Expose Title and other base fields in Manage Display Active

This could help move from DS to the Layout Builder

📌 Move enabling of the Display Suite module from dependencies: to install: in Varbase Core Fixed
📌 Move enabling of the Display Suite module from dependencies: to install: in Varbase Media Fixed