List five maintainability practices for CSS in a large organization.

List five maintainability practices for CSS in a large organization.

• A. Use design tokens, consistent naming (BEM/SMACSS), modular components, linting and code reviews, and maintain a central style guide/design system
• B. Use inline styles for everything
• C. Avoid linting
• D. Use CSS hacks

Answer: (A)

Maintaining CSS at scale relies on standardization and a modular, reusable codebase. Design tokens give a single source of truth for colors, typography, spacing, and other design values, making global changes easy and ensuring visual consistency across apps. A design system or central style guide ties these tokens to reusable components and patterns, providing governance that teams can follow at scale. Consistent naming conventions such as BEM or SMACSS reduce confusion and make selectors predictable, which speeds up development and reduces conflicts in large teams. Modular components enable building UIs from well-defined parts, so updates or style changes propagate through the system without touching every file. Linting and code reviews enforce agreed rules and quality standards, catching issues early and maintaining code health as the codebase grows. Inline styles undermine maintainability by mixing content with presentation, and they break reusability and theming. Skipping linting invites inconsistency and hidden regressions, while CSS hacks create brittle code that can fail as browsers evolve and across different teams’ work.

Maintaining CSS at scale relies on standardization and a modular, reusable codebase. Design tokens give a single source of truth for colors, typography, spacing, and other design values, making global changes easy and ensuring visual consistency across apps. A design system or central style guide ties these tokens to reusable components and patterns, providing governance that teams can follow at scale. Consistent naming conventions such as BEM or SMACSS reduce confusion and make selectors predictable, which speeds up development and reduces conflicts in large teams. Modular components enable building UIs from well-defined parts, so updates or style changes propagate through the system without touching every file. Linting and code reviews enforce agreed rules and quality standards, catching issues early and maintaining code health as the codebase grows.

Inline styles undermine maintainability by mixing content with presentation, and they break reusability and theming. Skipping linting invites inconsistency and hidden regressions, while CSS hacks create brittle code that can fail as browsers evolve and across different teams’ work.