Problem/Motivation
In #2575421: Add a Stable base theme to core and make it the default if a base theme is not specified (Change Record with mention) we decided to add Stable to be able to mark Seven and Bartik internal.
Problems we haven't still discussed:
- How should we apply changes for templates that are in Classy.
- How do we keep Bartik and Seven up to date. Right now they get left behind from Core because they are extending Classy and Stable.
Proposed resolution
- Create overriding template for both; Seven and Bartik. That is not optimal in terms of maintainability. It also doesn't make that much sense to improve markup for the internal themes if there is no way for anyone to utilize them. It also doesn't solve the problem where Seven and Bartik gets left behind from core markup.
- Create unstable Classy theme so that Bartik and Stable are not extending Classy and Stable anymore. Any changes for the templates would be done there so it wouldn't have to be done in both themes. After LTS we could just remove Classy and replace it with the unstable Classy. Problem with this is that it makes subtheming Seven and Bartik nearly impossible because after that you would have to copy both, unstable Classy and Seven as a base for your theme.
Remaining tasks
-
User interface changes
-
API changes
-
Data model changes
-
