Create new issues to refactor each page & files using Tools data

[t-will-gillis]

Dependency

• Identify which pages call Tools data from each project #4525

Overview

We need to create issues to refactor each of the pages identified in #4525 as a necessary step towards adding a Tools filter to the projects-check page per issue #4427

Action Items

• Using the list created in issue Identify which pages call Tools data from each project #4525, create a new issue for each list entry and itemize each new issue below.
  • Each issue should identify the page affected and the edits required in the file(s) that uses that page's Tools data.
  • Each new issue should be added as a separate entry to issue Add a Tools filter to the projects check page #4427 's list of dependencies.
  • New issues to create (edit as needed):
    • Refactor current-projects file to fix any formatting issue with new tools data format #4860 Projects page / current-projects.js
    • Refactor current-projects-check file to fix any formatting issue with new tools data format #4861 Projects-check page / current-projects-check.js
    • Refactor project page to fix any formatting issues with new tools data format #4859 project.html
    • other (if needed)

Resources/Instructions

• How to create issues

[github-actions]

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

[ronaldpaek]

1. 4/17-4/18
2. 4/18

[t-will-gillis]

Hi @ExperimentsInHonesty -
I moved this to 'In progress (actively working)' and removed the 'ready for dev lead' label: @ronaldpaek finished the preceding issue, and now would like to continue by writing the three new issues for this one.

[ronaldpaek]

@t-will-gillis @ExperimentsInHonesty I think I was able to complete this task, where should I move this issue / what column since I don't think I really made any PR's for this, I did update the label though

[t-will-gillis]

@ronaldpaek thanks- I linked the three issues to this issue in the comments and added them to the Project Board.

[github-actions]

@ronaldpaek

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. 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, June 27, 2023 at 12:17 AM PST.}

[ronaldpaek]

@t-will-gillis should i worry about this?

[t-will-gillis]

Closing this issue as completed- next steps are issues #4859, #4860, #4861