Refactor Tools data for brigade-organizers-playbook.md

[t-will-gillis]

Dependency

• Refactor current-projects file to fix any formatting issue with new tools data format #4860
• Refactor current-projects-check file to fix any formatting issue with new tools data format #4861

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

We need to revise the filter menu on the projects-check page to include a dropdown for "Tools", so that we can see where we might need to move project values from tools to technologies, and vice versa. In order for the filter to work properly, we need to refactor the tools data in the .md file from a string to a list.

Action Items

• Refer to the brigade-organizers-playbook.md file and find the entry for tools:
• Change the tools data from:

tools: Zoom, Calendly, Otter.ai, Google Docs, HackforLA.org guides

to

tools:
  - Zoom
  - Calendly
  - Otter.ai
  - Google Docs
  - HackforLA.org guides

• Confirm that the Tools data on all project pages is rendered correctly

Resources/Instructions

• Homepage
• Projects page
• This issue is part of an epic: Create new issues to refactor Tools data in project md files  #4777

[github-actions]

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

@PoppaRainmaker I am moving this issue to the in progress column. Please do that in the future when you take a new issue.

[github-actions]

@PoppaRainmaker

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 Tuesday, August 1, 2023 at 12:05 AM PST.}