Problem/Motivation
Drupal 8 introduced Stable theme as a backwards compatibility layer. This enabled us making disruptive markup and CSS changes in core and modules without breaking production themes. According to our original plan, all markup changes take place when a new major release gets released.
Since that plan was created, we’ve decided to make changes to our policies to make upgrading between major releases easier. Because there’s no defined way for following deprecations, testing markup and CSS changes can be hard.
Proposed resolution
There are at least a few actionable tasks we could work on:
- List all markup changes to core to build undestanding of disruptiveness.
- Ensure Classy fully supports core markup and provide a way for themes extending Classy run without Stable to allow testing.
- Create a plan for avoiding same from happening in Drupal 10
Remaining tasks
-
User interface changes
-
API changes
-
Data model changes
-