Epic: Create Issues to audit codebase for img tags ending with a slash

[roslynwythe]

Overview

We want to change each img HTML tag ending with a slash (<img.../>) in the HfLA codebase to an img tag without an ending slash (<img...>). An issue template and instructions will be prepared, in order to facilitate the creation of issues for performing the audit across the entire codebase. Each new issue will audit a single file and results will be stored in the HfLA-Website: img Tag Audit spreadsheet.

Action Items

• Make an issue template to audit, find, and document instance of <img.../> in each file in the HfLA-Website: img Tag Audit spreadsheet¹
  • This issue template will include a "Complexity: Small" label and a "ready for dev lead" label along with all the other needed labels.
• Review and (if needed) edit the following in the HfLA-Website: img Tag Audit spreadsheet:
  • "Instructions for Page Audit Issue Writers" section on the Instructions tab ¹
  • Page Audit tab ². All the files that still need to be audited are already listed in the Page Audit tab.
  • img with Ending Slash tab ³. This tab contains the lines of code with <img.../> that have been found so far. This tab will also be where developers auditing the files add their findings.
• Use the template to make one issue as an example
• Get approval from a PM on the template.

Resources/Instructions

• This epic resulted from Rollout Plan: Refactor code with img HTML tags to end without a slash #4362

Footnotes

1. HfLA-Website: img Tag Audit spreadsheet ↩ ↩²

2. HfLA-Website: img Tag Audit spreadsheet's Page Audit tab ↩

3. HfLA-Website: img Tag Audit spreadsheet's img with Ending Slash tab ↩

[github-actions]

Hi @roslynwythe, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)