Resolve "Potentially unsafe external link" in _includes/current-guides.html

[roslynwythe]

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.
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 need to fix a potentially unsafe external link by adding the attribute rel="noopener noreferrer". The problem and the solution is similar the those detailed in https://github.com/hackforla/website/security/code-scanning/3, however the instance addressed by this issue did not result in a CodeQL alert.

Action Items

• Open the file _includes/current-guides.html in your IDE
• Replace

                        <a href="{{item.resource-url}}" class="toolkit-flex-item-status" target="_blank">

with

                        <a href="{{item.resource-url}}" class="toolkit-flex-item-status" target="_blank" rel="noopener noreferrer">

• Using Docker, check the url /toolkit and check that the page remains the same in mobile, tablet, and desktop views as on the current website (See 2 in the Resources/Instructions section below). Refer to the Resources/Instructions section for a screenshot of the hyperlink modified in this issue (highlighted in yellow). Confirm that link still works.

Merge Team

• When this issue is completed, check off the issue in Epic: Create issues to resolve CodeQL alerts 1- 24, 98 "Potentially unsafe external link" #5129

Resources/Instructions

hyperlink modified in this issue

1. GitHub CodeQL documentation
2. Webpage: https://www.hackforla.org/toolkit
3. This issue is part of Epic: Create issues to resolve CodeQL alerts 1- 24, 98 "Potentially unsafe external link" #5129

[github-actions]

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

[DakuwoN]

Hello, I am available Monday - Friday after 1:30PM Eastern and Weekends anytime.
I will have this issue complete by Sunday.

[ExperimentsInHonesty]

@DakuwoN In future, please do not take issues from the new issue approval column. Only from the prioritized backlog.

[DakuwoN]

I'm sorry @ExperimentsInHonesty it's been so long, and I even re read the onboarding documents, I expect some other mistakes as well. Sorry again. Won't happen again.