💸 Tech Debt - 💄Styling Standards

Description
Currently, our website lacks standardized styling guidelines, leading to a situation where modifying one page affects others. This cycle of changes and fixes results in inconsistency and higher maintenance efforts.

Pain Points::

• Inconsistency
• Maintenance cost

Proposed solution

• Implement a consistent typography style by inheriting it for each component (using prose).
• Develop utility classes for creating components; changes to these classes should be subject to designer approval.
• Maintain a comprehensive list of pages that need testing whenever utility classes are modified.
• Prior to creating new utility classes, developers must ensure that the required utility class doesn't already exist.

This approach aims to establish uniform styling, reduce maintenance overhead, and streamline the development process.

The issue names no files, tests, or entry points. Start by locating the existing typography and utility-class definitions, then inventory the affected pages and current styling inconsistencies. Done should include an agreed styling standard, documented utility-class usage and approval expectations, and a page-testing list for utility-class changes.