Gutenberg is currently written primarily with Node entities in mind.
I think the module should be flexible enough to work with most (content) entity types e.g. Taxonomy terms.
As part of this work, I think we should move away from storing all the configurations in gutenberg.settings.yml and moving towards storing them as third_party_settings on the entity type and working from there.
This also makes it easier to map the configuration to
a schema →
rather than dynamically setting them.
https://www.drupal.org/project/config_inspector → may be used to inspect the configuration schema.
gutenberg.settings, and moving active Gutenberg settings into the appropriate node type third party settings.Yaml::decode rather than json_decode, YAML is way more human friendly to use and fits well with the Drupal ecosystem.Implement as part of the #3107797: Dynamic render blocks support (API rework using WordPress block parser rather than regex) → work.
N/A
gutenberg.settings configuration will be moved into the relevant node.type.$entity_type third_party_settings.Closed: duplicate
2.0
Code
The patch will have to be re-rolled with new suggestions/changes described in the comments in the issue.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
RE: #39 the patch doesn't support blocks, but I think it would be fantastic if that could be added to the scope. Having Gutenberg in blocks is a powerful page building asset.
This is a duplicate of #3445655 where we'll continue to work on this.