@Lindy and @Sheena,
The questions asked by Chris are mainly about visual style, not the naming of elements. Remember, 99% of our users will only experience the styles and not interact with the names directly. So our focus should remain on how these elements look and function rather than their class names.
---
Here is the longer, more technical explanation:
Class names are primarily used as identifiers for elements within the codebase, rather than literal descriptions of those elements. When you initially create class names, they often reflect the visual or functional characteristics of the components they style. For example, 'Rounded Green Box' was named when the box was rounded on all corners, the border was colored green, and the background what white.
However, as designs evolve, these visual or functional attributes might adjust. So now, the 'Rounded Green Box' only has rounded corners on the right, a light green background, and a dark green border on the left reflecting an updated design decision. Despite these changes, the original class name remains the same.
Renaming classes can lead to a cascade of updates across the entire project, which is both time-consuming and prone to error. Maintaining the original class names ensures consistency and stability in the code, especially for elements that are already widely used. The focus is on the style and maintainability rather than the literal accuracy of the names.