>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3445654. --> Reported by: [marcofernandes](https://www.drupal.org/user/2127558) Related to !298 !294 !284 !283 !281 !280 !279 !278 !277 !275 !276 !274 !273 !272 !271 !270 !269 !268 !267 !266 !258 !257 !251 !249 >>> <h2>Update Gutenberg core library to <del>21.9 (wp/6.9)</del> 22.6</h2> <p>21.9 is already in 4.0.x <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/gutenberg/issues/3464680" title="Status: Closed (fixed)">#3464680: Update Gutenberg core library (4.x)</a></span> but moving to 22.6 [<a href="https://git.drupalcode.org/project/gutenberg/-/merge_requests/251]">https://git.drupalcode.org/project/gutenberg/-/merge_requests/251]</a></p> <h2>API Changes<br> <h2> </h2></h2><p>Given that this is a fairly major update. It's also a good opportunity to clean up the API a bit, improving the general developer quality of life a fair bit as future work gets done.</p> <p>We can pull out the specific tasks into separate issues so it's easier to track.</p> <h3>Drop older Drupal support</h3> <p>It's worth <a href="https://endoflife.date/drupal">dropping support for older versions of Drupal</a> in this major update.<br> It should make maintainance a lot easier if we only have to worry about Drupal 11 compatibility going forward.</p> <p>At the very least, Drupal 9 support can be safely dropped.</p> <h3>Class-based Hooks</h3> <p>As part of the move towards Drupal 11 compatibility.</p> <p>We should migrate the procedural hooks/functions in favour of <a href="https://www.drupal.org/blog/drupal-11-1-0">the class-based one</a>.</p> <p>It should make code easier to use, support dependency injection, as well as allow patches to be made to different hooks with less conflicts.</p> <p>For additional details, see:<br> 1. <a href="https://www.drupal.org/node/3486534">https://www.drupal.org/node/3486534</a><br> 2. <a href="https://www.drupal.org/node/3442349">https://www.drupal.org/node/3442349</a></p> <h3>Block processors</h3> <p>This is a bit of technical debt realized after committing the original <a href="https://git.drupalcode.org/project/gutenberg/-/blob/119603d0/src/BlockProcessor/GutenbergBlockProcessorManager.php">block processor manager</a> as part of the <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/gutenberg/-/work_items/3107797" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/gutenberg/-/work_items/3107797</a></span> issue.</p> <p>Block processors should have been registered as <a href="https://www.drupal.org/docs/drupal-apis/plugin-api/annotations-based-plugins">annotation plugins</a> rather than the <code>gutenberg_block_processor</code> service collector we currently have.</p> <p>We should move towards the plugins-based approach since it makes it easier to work with the various Gutenberg plugins available (you can override existing plugins, or alter them as necessary).</p> <p>Upgrade path: Installations with custom processors will simply need to move their block processors into the appropriate <code>/src/Plugin/GutenbergProcessor/</code> type folder with the annotation, and remove the <code>services.yml</code> definition. This should ideally be documented in the release notes for 4.0.</p> <h2>Single Field Editor</h2> <p>Planned for 4.1.0</p> <p>This can take two approaches: Extend current editor plugin or create a field widget / editor (or both?).</p> <p>Currently Gutenberg is an editor plugin. To be applied to any text field. Should we keep it that way?</p> <h2>Entity Agnostic</h2> <p>Planned for 4.2.0<br> <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/gutenberg/issues/3445655" title="Status: Active">#3445655: Entity type agnostic</a></span><br> 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. </p> <p>Some discussions on these issues:</p> <ul> <li><span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/gutenberg/-/work_items/3163200" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/gutenberg/-/work_items/3163200</a></span></li> <li><span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/gutenberg/-/work_items/3345926" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/gutenberg/-/work_items/3345926</a></span></li> </ul> <p>Worth checking:</p> <ul> <li>Third-party settings provided by Drupal <a href="https://api.drupal.org/api/drupal/core!lib!Drupal!Core!Config!Entity!ThirdPartySettingsInterface.php/interface/ThirdPartySettingsInterface/8.2.x">https://api.drupal.org/api/drupal/core!lib!Drupal!Core!Config!Entity!ThirdPartySettingsInterface.php/interface/ThirdPartySettingsInterface/8.2.x</a> </li> <li>Layout Builder <a href="https://git.drupalcode.org/project/drupal/-/tree/10.4.x/core/modules/layout_builder?ref_type=heads">https://git.drupalcode.org/project/drupal/-/tree/10.4.x/core/modules/layout_builder?ref_type=heads</a></li> </ul> <h3>New field to store blocks</h3> <p>JSON field? <a href="https://www.drupal.org/project/drupal/issues/3343634">https://www.drupal.org/project/drupal/issues/3343634</a> </p> <p>Consider search index and JSON API integration</p> <p>Steps:</p> <ul> <li>Focus will be to make it agnostic. CodebyMikey made a while back an implementation on this branch <a href="https://git.drupalcode.org/project/gutenberg/-/tree/8.x-2.x-3163200-entity-agnostic?ref_type=heads">https://git.drupalcode.org/project/gutenberg/-/tree/8.x-2.x-3163200-entity-agnostic?ref_type=heads</a> (<a href="https://www.drupal.org/project/gutenberg/issues/3163200">https://www.drupal.org/project/gutenberg/issues/3163200</a>) 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.</li> <li>Make it possible to store the data in a structured way.</li> </ul> > Related issue: [Issue #3522739](https://www.drupal.org/node/3522739)