- Issue created by @danchadwick
Hey Dan,
A couple of notes on my end regarding the issue:
> Currently when a radix template changes, existing sites will not receive the change without manually copying the change from the starterkit to their sub-theme.
That's by design, and I believe that's okay to be like this, any older website that is already built, shouldn't be needing to change their markup (eg. templates and so on), so what they currently have should suffice. If they are keen on being updated, they should manually review and update if needed.
> When the change is accompanied by a corresponding change to the component, this can cause incompatibility where none would otherwise occur.
This is the tricky part, but we've been doing this since 8.x.4.x more or less, we just need to be more mindful of backward compatibility when changing the components.
> Also, core discovers the templates in the starterkit and uses them in the absence of a template in the sub-theme.
That's the core problem to be addressed, when we set the
starterkit: trueit should just ignore the templates, but for now let me take a look, I might have some solutions for this, eg. fully remove the starterkit once it gets copied