Contrib.social
Created on 7 May 2024, about 1 year ago

Entity Agnostic

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:

Worth checking:

New field to store blocks

JSON field? https://www.drupal.org/project/drupal/issues/3343634 ✨ Add "json" as core data type Active

Consider search index and JSON API integration

Steps:

Single Field Editor

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

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

Extend block-editor component

🌱 Plan
Status

Active

Version

3.0

Component

Code

Created by

🇵🇹Portugal marcofernandes

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024