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.

Note: We are going to try and have this issue as the one and only code cleanup meta issue for Bartik. Problem/Motivation Bartik's template files need to be assessed and cleaned up of redundant markup, bad formatting and ID's. Bartik's CSS files need to follow Drupal's CSS Coding Standards. Proposed resolution General cleanup [#1903048] [#2395825] [#2399709] [#2398447] [#2396489] [#2548805] [#2399247] Refactor CSS into components (current focus) Also next we are raising issues based specifically around the CSS files in Bartik that were created in [#2375673].