Open alisonjo315 opened 2 years ago
I think we should go for it.
we're pretty clear with everybody that cwd_base updates are not necessarily backwards compatible.
And, we can put a big note in the release notes. If we want, we can even bump the semantic version up to 3.x ^^ If we do that, we could take some other liberties, like...
Our norm these days is to put site footer "stuff" in html.html.twig (usually by way of a partial/include template called site-footer.html.twig).
But, cwd_base puts it in page.html.twig.
I recommend we move this code to html.html.twig!
Reasons:
Problem: Not backwards-compatible 😕 If an existing site uses cwd_base/page.html.twig (i.e. if they don't have a template override in their child theme
*
), their footer will get messed up if they update cwd_base.*
We don't need to worry about child themes using cwd_base/page.html.twig with block overrides or include variables, because it doesn't have any such things.