We have some settings around this that can be hard coded like "hey let's only enable these 10 blocks" but not really a "keep the 20 you have given me but mix in these 5 that I made". This would allow an organization / user implementing HAX to...
get HAX and all our defaults we ship
build their own stuff using open-wc style tooling / recommendations
place that output in a location like _config/js-assets or something similar
those blocks/themes discovered in that directory automatically become available
To make this possible...
system needs a connotation of autoloading whats in that directory and injecting it. wc-autoloader supports multiple registries (thank you past me) so it could be just shipping the default but then injecting additional if they exist
This injected approach should be built automatically by reading the directory structure or a configuration file the tooling makes
The tooling could operate like wc-registry as far as how it's built but the target is slightly different as far as audience and directory output
custom-blocks.json coming from config would allow for loading the known additional elements to auto turn on and be selectable in HAX editor without modifying the other file
custom-themes.json coming from config would allow for loading the known additional themes discovered to auto turn on but also be available for selection in the system
This starts taking the customization / working with HAX to extend it into the territory of JS tooling person and another step away from PHP / manual configuration even if just a small one.
We have some settings around this that can be hard coded like "hey let's only enable these 10 blocks" but not really a "keep the 20 you have given me but mix in these 5 that I made". This would allow an organization / user implementing HAX to...
_config/js-assets
or something similarTo make this possible...
custom-blocks.json
coming from config would allow for loading the known additional elements to auto turn on and be selectable in HAX editor without modifying the other filecustom-themes.json
coming from config would allow for loading the known additional themes discovered to auto turn on but also be available for selection in the systemThis starts taking the customization / working with HAX to extend it into the territory of JS tooling person and another step away from PHP / manual configuration even if just a small one.