At the moment I assume that sooner or later working on the chronicle configs will become more complicated if the canvas concept continues to be used as is.
Possible new approach:
Add new section "canvas" to templates, besides "presets", "contents", etc.
Entries in "canvas" section are named and have a subcanvas relation. Not necessarily expressed in the yaml structure, but perhaps similar to the "Inherit" entry.
Content entries get an additional field "canvas" that denotes a canvas ID
To modify a canvas in a template that inherits from one of the main templates: This is either done via presets as before, or canvases with the name ID in the child take precedence during inheritance
At the moment I assume that sooner or later working on the chronicle configs will become more complicated if the canvas concept continues to be used as is.
Possible new approach: