Skip to content

Prepare this epic with issues

Instructions for Completing the CSS Cleanup Spreadsheet

This document outlines the steps for completing the CSS cleanup spreadsheet to prepare for the frontend CSS cleanup initiative. Your contributions will help improve the performance, maintainability, and overall quality of GitLab's frontend codebase.

Spreadsheet Link: https://docs.google.com/spreadsheets/d/1Nvu02aE17VVzb0LLButeUm-DHkUm-TyUHZ1cJ9fZuc0/edit?gid=0#gid=0

Sheet: 'All Framework Classes'

Steps:

  1. Review each row in the spreadsheet. Each row represents a CSS class within GitLab's frontend framework.

  2. Determine the fate of each class:

    • If the class should remain as is, mark the "Keep it as is" checkbox.
    • If the class should be deleted or moved, mark the "Delete or Move it" checkbox.

  3. Assess community contribution suitability:

    • If the task of deleting or moving the class is appropriate for a community contributor, mark the "Is Appropriate for community contributor" checkbox.

  4. Adjust the weight estimate (if necessary):

    • Review the "Weight Estimate" column. This provides an initial estimate of the task's complexity (1-4).
    • If you believe the weight should be adjusted based on your understanding of the class and its usage, update the value accordingly.

  5. Note: The values in the "Attribute Count," "Sub Class Count," and "Usage Count" columns may contain inaccuracies. Please use these values as rough estimates when making your assessments.

Important Considerations:

  • Prioritize classes that are unused or have minimal usage for deletion or refactoring.
  • Consider the potential impact of removing a class on other parts of the application.
  • If a class is used in multiple places or has complex dependencies, it might be more suitable for a GitLab team member to handle.

Your careful evaluation and contributions will be invaluable in making this CSS cleanup project a success!

Edited by James Rushford