Create Issues to add new variable github-handle for members in design-systems.md

[roslynwythe]

Prerequisites

1. You must be a member of Hack for LA to work on an issue. If you have not joined yet, please follow the steps on our Getting Started page.
2. Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.

Overview

As developers we need to create issues to update each project team member in civic-tech-index.md with a the new github-handle variable, that will eventually replace the github and picture variables, reducing redundancy in the project file.

Action Items

• [ ] For each team member listed in _projects/design-systems.md that does not have a variable github-handle, create an issue using the template
• [ ] For each issue:
  • [ ] In the title, replace [INSERT MEMBER NAME] with the member's name
  • [ ] In the title, replace [INSERT PROJECT FILE] with design-systems.md
  • [ ] Under Action Items, replace [INSERT MEMBER NAME] with the member's name (in 2 places)
  • [ ] Under Action Items, replace [INSERT PROJECT FILE] with design-systems.md
  • [ ] Under Resources, replace [INSERT-PROJECT-FILE] with design-systems.md
  • [ ] Under Resources, replace [INSERT-PROJECT-FILENAME-WITHOUT-.MD-EXTENSION] with design-systems
  • [ ] Apply the following labels: "ready for dev lead", "good first issue", "role: front end", "role: back end/devOps", "size: 0.25pt", "P-Feature: Project Info and Page"
  • [ ] List the issue number in #5441 under Good First Issues
• [ ] When all issues have been created and listed, move this issue to the "Questions/In Review" column of the Project Board, and apply the label "ready for dev lead"

Resources/Instructions

https://github.com/hackforla/website/wiki/project.md-file-template https://jekyllrb.com/ Webpage: https://www.hackforla.org/projects/food-oasis

• This issue is part of #5441

[github-actions[bot]]

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

[github-actions[bot]]

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

[github-actions[bot]]

Hi @dcotelessa, 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]

@dcotelessa Hope you are having a good holiday... Please let us know if you will be able to get this issue done before end of day August 4th. Sorry for the pressure but we are short of good first issues for the new people who will joining on August 5th.

[github-actions[bot]]

@dcotelessa

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 Tuesday, July 30, 2024 at 12:05 AM PST.}

[github-actions[bot]]

@dcotelessa

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 Tuesday, August 6, 2024 at 12:04 AM PST.}

[roslynwythe]

Hi David, if you are planning to complete this issue please leave an update using the guidelines provided in the github-actions bot message. If no update is provided by 8/13, you will be unassigned from this issue. Note that you do not have to generate issues for any of the items that already contain the key 'github-handle, and the issues that you create do not have to provide any values for github-handle`. Thank you!

[HackforLABot]

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

[dcotelessa]

Avaliability: Thu-Fri 11-4pm PST ETA: 2 hours

[t-will-gillis]

Hey @dcotelessa The issues you created look great, and I see that you added the links to 5441. Thanks so much for taking care of this!

Closing this issue as completed.