hackforla / website

Hack for LA's website
https://www.hackforla.org
GNU General Public License v2.0
293 stars 722 forks source link

Rollout Plan: Refactor HTML to resolve HTML linter errors #5277

Open roslynwythe opened 10 months ago

roslynwythe commented 10 months ago

Dependency

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[^1]

Action Items

Resources/Instructions

[^1]:HfLA audit HTML spreadsheet [^2]:HTML ESLint

github-actions[bot] commented 10 months ago

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:

github-actions[bot] commented 3 months ago

Hi @roslynwythe, HfLA appreciates your interest in this issue, but please note that it is in the New Issue Approval column of the Project Board because it has not been finalized, approved or prioritized, and so it is not ready for assignment. For this reason, you have been unassigned from this issue. Please remember to assign issues only from the Prioritized Backlog column. The one exception to this rule is if you are writing an issue and the Draft label is applied.

github-actions[bot] commented 4 weeks ago

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 :)

ExperimentsInHonesty commented 4 weeks ago

@roslynwythe please add the actual issues to the dependencies and then stick in the icebox