Problem/Motivation During the Drupal 8 life cycle, we have been unable to make improvements to Classy because of backwards compatibility concerns. When talking with members of the frontend community, many people recognize themselves in a situation where they are using Classy, but they've ended up overriding most if not all templates. Proposed resolution Replace Classy with a new starter kit theme. The starter kit markup and CSS will be allowed to change over time since it acts only as a starting point for themes.

Problem/Motivation Classy, which is the current base theme provided by core is stale because most changes are not allowed to retain backwards compatibility. We need to retain backwards compatibility because some design requirements of themes depending on Classy could depend on markup and/or CSS provided by Classy. While reviewing different approaches, we talked to members of the frontend community. Something that came up was that many of them recognize themselves in a situation where they are using Classy, but they've ended up overriding most if not all templates.