Just like it says. If we mark something as a Concept or Region #1924 . What we're really talking about is an "Entity type" field that goes off of page break which has implications for defaults much like #1704
This effectively implements the #1880 concept but its not a block in the page. Instead...
pages are nodes are entities. And entities default state is a piece of content in the site with default fields that can be visualized alla #1818
IF a page is changed from it's default entity type, it could still be a page, but it has config level implications for the site
Changing a page to an entity type "Taxonomy" could expose the listing of "Taxonomies" when something int he system wants that type of config data presented
Add color value to the entity -- #1930 and then we can associate name + color + icon to how the site leverages this entity within the site itself
initial entity types
page (or null, default)
taxonomy
term (in taxonomy)
region
this could set conceptual ground work for remote loaded / assessed entity data like user, file, etc that dont need to be loaded into site.json but could still be useful
Just like it says. If we mark something as a Concept or Region #1924 . What we're really talking about is an "Entity type" field that goes off of page break which has implications for defaults much like #1704
This effectively implements the #1880 concept but its not a block in the page. Instead...
Add color value to the entity -- #1930 and then we can associate name + color + icon to how the site leverages this entity within the site itself
initial entity types
this could set conceptual ground work for remote loaded / assessed entity data like user, file, etc that dont need to be loaded into site.json but could still be useful