Gutenberg 4

Entity Agnostic

📌 Entity type agnostic Active
This will allow Gutenberg to be used independent of the parent entity type, increasing flexibility and compatibility across various Drupal entities (Ex: Taxonomies). Consider also dropping the support for text field and add support for a dedicated field for blocks. For example custom entitites, taxonomies, products or groups, config entities, webforms. Or configuration form(emails with tokens and so on. Then you export that to config and deployed to environments.) So when activating Gutenberg, you typically go to a entity edit form, like for nodes.

Some discussions on these issues:

• 📌 Make Gutenberg entity-type-agnostic Needs work
• ✨ Integration of Gutenberg with Paragraphs and/or fields - All the UX difficulties Drupal has Active

Worth checking:

• Third-party settings provided by Drupal https://api.drupal.org/api/drupal/core!lib!Drupal!Core!Config!Entity!Thi...
• Layout Builder https://git.drupalcode.org/project/drupal/-/tree/10.4.x/core/modules/lay...

New field to store blocks

JSON field? https://www.drupal.org/project/drupal/issues/3343634 ✨ Add "json" as core data type to Schema and Database API Needs work

Consider search index and JSON API integration

Steps:

• Focus will be to make it agnostic. CodebyMikey made a while back an implementation on this branch https://git.drupalcode.org/project/gutenberg/-/tree/8.x-2.x-3163200-enti... ( https://www.drupal.org/project/gutenberg/issues/3163200 📌 Make Gutenberg entity-type-agnostic Needs work ) but it never got merged. Now let's try to deliver an update but with smaller change increments so it's easier to test and merge.
• Make it possible to store the data in a structured way.

Single Field Editor

This can take two approaches: Extend current editor plugin or create a field widget / editor (or both?).

Currently Gutenberg is an editor plugin. To be applied to any text field. Should we keep it that way?

Update Gutenberg core library to 18.5 (wp/6.6)

There's some points to consider with the upgrade:

• Synced patterns editing: The functionality to edit a synced pattern on the editor was removed - a lot of users/editors weren't aware that editing a synced pattern would affect all pages where the pattern was used.

Extend block-editor component