Remove unused alt-hero field from expunge-assist.md project file

[JessicaLucindaCheng]

Overview

As a developer, I want to make sure unused code is removed from the codebase in project cards so that

• time to load the website is as low as possible,
• it's easier to understand the code, and
• time to review the code is reduced.

Details

In project md files, image-hero is a decorative background image and alt-hero is the alt text associated with image-hero. However, alt-hero text is not used anywhere in our codebase since the image-hero is used as an SCSS background image.

Moreover, if the image-hero were to be used in an img HTML tag in the future, the alt text for all the image-hero images would be alt="", which could be set programmatically for all the alt properties associated with each image-hero.

Action Items

• For the file _projects/expunge-assist.md, remove line 9 for the alt-hero

alt-hero: 'Expunge Assist project logo'

• Once the pull request associated with this issue is approved and merged, please update and edit epic Remove unused alt-hero in project md files #2722 by
  • Checking off the dependency for this issue
  • If all dependencies are checked off, please move issue Remove unused alt-hero in project md files #2722 to the New Issue Approval column and remove the Dependency label

Resources/Instructions

• This issue is part of epic Remove unused alt-hero in project md files #2722

File and code links you will need to work on this issue

• Directory to find the page once you have it in your IDE: _projects/expunge-assist.md
• Click on the link below to see the source file code:
  

  website/_projects/expunge-assist.md

  Line 9 in fdecdb4

  alt-hero: 'Expunge Assist project logo'

Information about WCAG

• WCAG
• Web Accessibility Tutorials: Decorative Images

[rolzar]

Availability: 5 hrs.
ETA: 10/7.

[bishrfaisal]

Hey @rolzar, we see that you have taken up your second issue. Awesome work so far! It has been 2 weeks since you self-assigned, have you run into any obstacles? If so, please let us know and we would be happy to help!

[github-actions]

@rolzar

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 developer meeting discussion column 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.

_{You are receiving this comment because your last comment was before Tuesday, October 18, 2022 at 12:33 AM PST.}

[bishrfaisal]

Hi @rolzar! We haven't heard from you since October 4th (19 days ago). Hope you are okay. We have un-assigned you from this issue. Please feel free to pickup a new issue from the prioritized backlog when you return!

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

[roslynwythe]

Availability: 10/27, 10/28 daytime, 10/29 evening, 10/30 ETA: 10/30

…

On Thu, Oct 27, 2022 at 12:01 AM github-actions[bot] < ***@***.***> wrote: Hi @roslynwythe <https://github.com/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 :) — Reply to this email directly, view it on GitHub <#3196 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABIRM2PNBQPJ7DOKO55P6D3WFISEJANCNFSM5XX7XKVA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[roslynwythe]

I'm still proceeding down the pre-work checklist and just learned that not supposed to assign a "good second issue" until my first issue PR has been merged, so therefore I am unassigning myself.

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

[roslynwythe]

Availability: daytime 10/28, all day 10/30 and 10/31 ETA: 10/31

…

On Fri, Oct 28, 2022 at 11:34 AM github-actions[bot] < ***@***.***> wrote: Hi @roslynwythe <https://github.com/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 :) — Reply to this email directly, view it on GitHub <#3196 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABIRM2IXDYB4U4YQWGGS4O3WFQMBVANCNFSM5XX7XKVA> . You are receiving this because you were mentioned.Message ID: ***@***.***>