Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
2 of 5 tasks
roslynwythe opened this issue Aug 21, 2023 · 4 comments
Open
2 of 5 tasks

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

roslynwythe opened this issue Aug 21, 2023 · 4 comments
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Dependency An issue is blocking the completion or starting of another issue Draft Issue is still in the process of being created Feature: Refactor HTML Issue Making: Level 5 Make a Rollout Plan that has >1 epics to achieve and timelines for interdependencies role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less size: 0.25pt Can be done in 0.5 to 1.5 hours
Milestone
x. Technical debt

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Aug 21, 2023 •
edited by ExperimentsInHonesty
Loading

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 spreadsheet1

Action Items

  • Select an HTML linter and appropriate configuration settings
    • Consider HTML ESLint2, HTMLHint3
  • Create HfLA audit HTML spreadsheet1
  • Populate the HfLA audit HTML spreadsheet1 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 ↩3

  2. HTML ESLint ↩

  3. HTMLHint ↩
@roslynwythe roslynwythe added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Aug 21, 2023
@github-actions

This comment was marked as outdated.

Sign in to view
@roslynwythe roslynwythe added Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Issue Making: Level 2 Make issue(s) from an ER or Epic Issue Making: Level 4 Create an Epic Issue, and it's Level 2 or 3 issues role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers role: BA Business Analyst size: 0.5pt Can be done in 3 hours or less size: 0.25pt Can be done in 0.5 to 1.5 hours Feature: Refactor HTML and removed Complexity: Missing Issue Making: Level 2 Make issue(s) from an ER or Epic role: BA Business Analyst role: back end/devOps Tasks for back-end developers Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing labels Aug 21, 2023
This was referenced Aug 21, 2023
Closed
Open
@anjolaaoluwa anjolaaoluwa added this to the x. Technical debt milestone Aug 27, 2023
@roslynwythe roslynwythe self-assigned this Apr 1, 2024
@roslynwythe roslynwythe added the Draft Issue is still in the process of being created label Apr 1, 2024
@github-actions GitHub Actions

This comment was marked as outdated.

Sign in to view
@ExperimentsInHonesty ExperimentsInHonesty added Issue Making: Level 5 Make a Rollout Plan that has >1 epics to achieve and timelines for interdependencies and removed Issue Making: Level 4 Create an Epic Issue, and it's Level 2 or 3 issues labels Jun 5, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the Dependency An issue is blocking the completion or starting of another issue label Jun 11, 2024
@github-actions GitHub Actions
Copy link

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

This comment was marked as outdated.

Sign in to view
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Dependency An issue is blocking the completion or starting of another issue Draft Issue is still in the process of being created Feature: Refactor HTML Issue Making: Level 5 Make a Rollout Plan that has >1 epics to achieve and timelines for interdependencies role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less size: 0.25pt Can be done in 0.5 to 1.5 hours
Projects
P: HfLA Website: Project Board
Status: Ice box
Milestone
x. Technical debt
Development

No branches or pull requests
3 participants
@roslynwythe @ExperimentsInHonesty @anjolaaoluwa