Rollout Plan: Refactor HTML to resolve HTML linter errors

[roslynwythe]

Dependency

• Epic: Create template, spreadsheet and list of issues for spellcheck audit #5248
• Epic: Manage CodeQL deployment #5005

Overview

We aim to make use of an HTML linter to improve the quality, consistency and appearance of our HTML markup. We will audit every page containing html markup, record errors and create issues to resolve the errors using the HfLA audit HTML spreadsheet¹

Action Items

• Select an HTML linter and appropriate configuration settings
  • Consider HTML ESLint², HTMLHint³
• Create HfLA audit HTML spreadsheet¹
• Populate the HfLA audit HTML spreadsheet¹ with the filepath of each html file in the codebase
• Create Epic to create issues to audit each page and record errors
• Create Epic to create issues to fix errors see Epic: Create Issues to Fix HTML linter errors #5279

Resources/Instructions

Footnotes

1. HfLA audit HTML spreadsheet ↩ ↩² ↩³

2. HTML ESLint ↩

3. HTMLHint ↩

[github-actions]

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:
Complexity, Role, Feature

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels