Add a single XB Page entity by default, for use within the XB demo

In current MR, I am not able to import content added in recipes/drupal_cms_xb/content/xb_page/20354d7a-e4fe-47af-8ff6-187bca92f3f7.yml. I am getting error ResponseText: Drupal\Core\DefaultContent\InvalidEntityException: /var/www/html/vendor/composer/../..//recipes/drupal_cms_xb/content/xb_page/20354d7a-e4fe-47af-8ff6-187bca92f3f7.yml: components.0=The array must contain a "tree" key.||components.0=The array must contain a "props" key. in Drupal\Core\DefaultContent\Importer->importContent() (line 113 of /var/www/html/web/core/lib/Drupal/Core/DefaultContent/Importer.php).

Currently, I am doing the steps below to make this MR somewhat work.

• Rename recipes/drupal_cms_xb/content to recipes/drupal_cms_xb/content_old
• Run ddev rebuild && ddev launch in terminal and follow steps of installation
• Run ddev drush php:eval "(\Drupal\experience_builder\Entity\Page::create(['type' => 'xb_page', 'title' => 'Test']))->save();" in terminal
• cd web/modules/contrib/experience_builder/ui
• npm install && npm run drupaldev
• Visit https://drupal-cms-dev.ddev.site/xb/xb_page/1/editor. This also gives console warning Warning: Each child in a list should have a unique "key" prop.

With latest commit https://git.drupalcode.org/issue/drupal_cms-3495711/-/commit/4fbe9a9586e..., now there is only one issue in this integration. I am not able to import default content added in content/xb_page and getting same error as in #3

Steps to make current MR work:

• Rename recipes/drupal_cms_xb/content to recipes/drupal_cms_xb/content_old
• Run ddev rebuild && ddev launch in terminal and follow steps of installation
• Run ddev drush php:eval "(\Drupal\experience_builder\Entity\Page::create(['type' => 'xb_page', 'title' => 'Test']))->save();" in terminal
• Visit https://drupal-cms-dev.ddev.site/xb/xb_page/1/editor.

This is blocked by a bug in XB: 🐛 Core's default content importer fumbles Experience Builder field data Active

To help move the implementation of Olivero components for XB forward, I'm committing your work to add the XB dependency over in ✨ Add Experience Builder as a dev dependency Active , so that can be removed from this MR.

We can commit this, I think, if we patch Experience Builder with 🐛 Core's default content importer fumbles Experience Builder field data Active . Since it's currently a dev dependency, that's allowable.

I got this to work and so I'll commit it to accelerate the development of components. We'll move the Experience Builder dependency and the xb_page entity into drupal_cms_starter in a follow-up once we have the blockers in.

Alright - merged into 1.x. This oughta help the heroic frontenders who are working to implement the components for XB!

Automatically closed - issue fixed for 2 weeks with no activity.