hackforla / website

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

Refactor HTML to resolve linter error: _guidepages/2FA.html - line 45 #5710

Closed roslynwythe closed 7 months ago

roslynwythe commented 1 year ago

Prerequisite

  1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page and attend an onboarding session.
  2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

Overview

We want to update an HTML tag to resolve the linter error "Value of attribute [class] must be in double quotes"

Action Items

Merge Team

Resources/Instructions

  1. For QA to validate change: https://github.com/hackforla/website/blob/gh-pages/_guidepages/2FA.html
  2. Webpage: https://www.hackforla.org/guide-pages/2FA
  3. This issue is tracked in HfLA-Website: HTML linter audit spreadsheet, and #5279
github-actions[bot] commented 1 year 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 9 months ago

Hi @thisisdientran, 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 :)

thisisdientran commented 9 months ago

ETA: Jan 23rd

github-actions[bot] commented 8 months ago

@thisisdientran

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, January 22, 2024 at 11:05 PM PST.

github-actions[bot] commented 8 months ago

@thisisdientran

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, January 29, 2024 at 11:06 PM PST.

thisisdientran commented 8 months ago

Hi Hackforla/Website Team,

I am sorry for missing the deadline, as I have constant exams and writing assignments recent weeks. I have a hard time on dealing with them.

I will fill the template for late within Sunday. Please allow me to postpone the deadline until the end of the next week.

Best regards, Tuan Dien Tran Tel: 6268786378 Linkedin: linkedin.com/in/trantuandien/

On Fri, Feb 2, 2024 at 2:08 PM github-actions[bot] @.***> wrote:

@thisisdientran https://github.com/thisisdientran

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here https://github.com/hackforla/website/issues/1619#issuecomment-897315561 and here https://github.com/hackforla/website/issues/1908#issuecomment-877908152 are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, January 29, 2024 at 11:06 PM PST.

— Reply to this email directly, view it on GitHub https://github.com/hackforla/website/issues/5710#issuecomment-1923134500, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOIKZMMTZXX5CWF7H3UBYTLYRSGG5AVCNFSM6AAAAAA6BSG6XOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRTGEZTINJQGA . You are receiving this because you were mentioned.Message ID: @.***>

github-actions[bot] commented 8 months ago

@thisisdientran

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, February 12, 2024 at 11:05 PM PST.

LRenDO commented 8 months ago

Hi @thisisdientran! Thanks for working on this issue. If you're still working please add an update. If you're not able to continue to working on it, leave us a comment to let us know. If we don't hear from you soon, we will remove you from the issue. Thanks!

github-actions[bot] commented 8 months ago

@thisisdientran

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, February 19, 2024 at 11:06 PM PST.

ExperimentsInHonesty commented 7 months ago
github-actions[bot] commented 7 months ago

Hi @nelsonuprety1, 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 :)

nelsonuprety1 commented 7 months ago

Availability: March 2, 2024 ETA: March 2, 2024

github-actions[bot] commented 7 months ago

Hi @Ayrh1, 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 :)

Ayrh1 commented 7 months ago

Availability for this week: thursday evening 5hours, friday 8+ hours afternoon to late evening My estimated ETA for completing this issue: first issue ever, 2hrs, to make sure i did it right