search

unlcms / project-herbie

Drupal 10 implementation at the University of Nebraska–Lincoln
https://cms.unl.edu
GNU General Public License v2.0
5 stars 6 forks source link

Determine which block.block.* config to ignore #177

Closed macburgee1 closed 4 years ago

macburgee1 commented 4 years ago

Block configuration presents somewhat of a challenge. Some block configuration, such as unl_five_herbie_content and unl_five_herbie_branding are clearly global configuration and are something we'll want to manage with version control. Other block configuration, such as a particular site's Contact Us block, is specific to the site and is not something we want to export or to manage with version control.

We need to decide whether to adopt a whitelist or blacklist approach for ignoring block configuration. The only workable solution I see is to adopt a blacklist approach where all block configuration is ignored, except for unl_five_herbie_content, unl_five_herbie_branding, etc.

macburgee1 commented 4 years ago

To get the list of block config to be version controlled, I installed a vanilla version of Project Herbie from master branch HEAD.

ericras commented 4 years ago

How will this jive with the contact blocks?

macburgee1 commented 4 years ago

Contact blocks will be ignored for config export/import. Effectively, they'll be treated like content, not config.