Problem/Motivation
The varbase_content_base recipe currently installs and relies on the core block_content module, along with its related field storages, field instances, form/view displays, and base field
overrides for the basic block type. Since Drupal Canvas now handles block-like content through its own components and global page regions, block_content is no longer needed in Varbase, and its presence
adds unused configuration and noise to content tracking (Entity Usage).
In addition, the newly introduced edit canvas global regions permission (Drupal Canvas issue #3584713: Add "Allow Edit Global Regions" permission to restrict editing of global page regions ) is not yet granted to the content_admin role in the recipe, so content administrators cannot edit global Canvas regions (header, footer, etc.) out of the box.
Proposed resolution
block_content from the install list in recipe.yml.block_contentfield.storage.block_content.field_description from the recipe's import list.block_content from track_enabled_source_entity_types and track_enabled_target_entity_types in config/entity_usage.settings.yml.administer page template permission from the content_editor role (reserved for admin-level users).edit canvas global regions permission to the content_admin role in recipe.yml.config/system.menu.social-media-menu.yml to provide a default Social Media menu used by Varbase content structure.Remaining tasks
- ✅ File an issue about this project
- ✅ Addition/Change/Update/Fix to this project
- ✅ Testing to ensure no regression
- ✅ Automated unit/functional testing coverage
- ➖ Developer Documentation support on feature change/addition
- ➖ User Guide Documentation support on feature change/addition
- ➖ UX/UI designer responsibilities
- ➖ Accessibility and Readability
- ✅ Code review from 1 Varbase core team member
- ✅ Full testing and approval
- ✅ Credit contributors
- ✅ Review with the product owner
- ✅ Update Release Notes
- ❌ Release varbase-11.0.0-alpha1, varbase_starter-1.0.0-alpha1, varbase_content_base-1.0.0-alpha1
User interface changes
Content administrators can now edit global Drupal Canvas page regions (header, footer, etc.). The legacy custom "Basic block" type and its fields are no longer provisioned by the recipe.
API changes
- N/A
Data model changes
The recipe no longer installs block_content-related configuration. Existing sites already using custom blocks are unaffected because recipes do not uninstall modules; this only changes behavior for new
installs applying the recipe.
Release notes snippet
- feat: #3584733 Add edit canvas global regions permission to content and site admin roles and remove block_content usage from Varbase Content Base recipe
Comments
Comment #2
rajab natshahComment #4
rajab natshahComment #5
rajab natshahComment #7
rajab natshah✅ Released varbase_content_base-1.0.0-alpha1