[wp-trac] [WordPress Trac] #49637: Create a report outline for CSS audit

[WordPress Trac]

#49637: Create a report outline for CSS audit
-----------------------------------+-----------------------------
 Reporter:  notlaura               |      Owner:  (none)
     Type:  enhancement            |     Status:  new
 Priority:  normal                 |  Milestone:  Awaiting Review
Component:  Administration         |    Version:
 Severity:  normal                 |   Keywords:
  Focuses:  css, coding-standards  |
-----------------------------------+-----------------------------
 This ticket is under the umbrella CSS audit ticket #49582, and is for
 creating a report outline for the audit.

 The work to create a report outline consists of:

 * Decision making regarding what the report should contain,
 * Creating follow-up tickets for collecting data to populate the report,
 * Creation of a "Report Outline Document" or similar, that can be updated
 with results or changes in requirements as the audit is performed.

 The report outline document is essentially a list of what we want to know
 as a result of the audit. For example:

 * Determine method of categorization of existing CSS (e.g. by files, area
 in admin)
 * Category (from above) that contains highest specificity
 * List of unique values for each of a list of properties, and number of
 occurrences
 * Locations and total count of `!important`s
 * State of CSS comments in each of the categories
 * Location of outdated or brute-force layout practices (e.g. floats,
 positioning and pixel nudging)
 * Longest selector

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49637>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform