allow for setting colors in site-config relative to theme, global, or type specific

[btopro]

1930 #1880

If we have both of these then we can start to make a schema for site config to set colors for the theme based on type or globally like 'accent color' or 'heading style'. First we need to think of all the settings that would go into this object, then where this object gets stored. Is it in site settings cluster of values? (possible) or an 'element' in the theme that's written to a specific file.

The first is easier obviously, but the second, a specific 'global config' region of sorts would open up the possibility of loading other values and solving things like loading JS on every page (alla #1870 ) as well as future capabilities like the AI chat bot which would need to be loaded in somewhere.

If we made another folder off of the element called system this could set the stage for the #1608 as well. Things we'd store in this folder:

• The single site loading PHP script that we have a proof of concept of that needs worked in
• region based data #1924 so that it is name spaced system/regions/header.html as opposed to in site.json like currently
• system/regions/regions.json - quick look up for all the metadata associated with these regions as far as which ones exist (bc we can't poll the file system or. we could but they are just blank and if a theme uses them then it creats the file on the fly perhaps #1782 )
• system/global.html which could include the global non-visual 'region' that is for injecting things globally like the color settings for config among other things

[btopro]

site config as currently defined, could be configurable based on extending entity types and leveraging them. Right now the #1934 starts setting the stage for this though it's not fully implemented yet