EPIC: Prepare the Project Pages page for Homepage Launch

### Overview
We need to track existing issues and make new issues to deliver Project Pages page complete enough for the Homepage launch

#### Details
We need to track and support the final wrap up items for the homepage launch, so that it can be completed.

### Action Items
- [x] List all the issues related to the label
- [x] Identify what open issues have to be resolved before launch, by classifying the issues into the following categories using MoSCoW method in a comment.
- Must Have
- Should Have
- Could Have
- Won't Have this time
- [x] Add the following details under each issue
```
- why: [ADD WHY ITS IMPORTANT TO TO THE LAUNCH]
- status: [ADD STATUS e.g., Icebox, Emergent Requests, New Issue Approval, ERs and epics that are ready to be turned into issues, Prioritized Backlog, In Progress (actively working), Questions / In Review]
- draft: [true OR false]
- responsible: [ADD GITHUB HANDLES WITHOUT @]
- role: [ADD ROLE e.g. data scientist, infrastructure, design, design lead, user research, Research Lead, dev leads, data analyst, BA, hfla leadership, back end/devOps, writing, front end, merge team, technical writer]
```
- [x] Once you receive sign-off from Staff PM add to `## Relevance of the issues to the Homepage launch`
- [x] Review comments with `Notes carried forward from epic` if it exists, and make sure all previous items are addressed in the top of the issue.
- If it specifies new issues to make then add explicit action items for making those issue in a new comment on this issue
- get sign-off on those new issues to make by Staff PM
- [x] Identify items that need issues opened by looking at the page and features and seeing what is not already addressed by the existing issues or new issues to make list.
- [x] Make the issues specified
- [x] Link them as sub issues to this issue
- [x] Classify them using MoSCoW and add the details (why, status, draft, responsible, role)
- [ ] Get Sign-off and prioritization of the issues by Staff PM
- [ ] If this page has content that must be checked for accuracy before homepage launch, add the detail to the epic for tracking that (resource 1.05)

### Resources/Instructions
- Parent Epic: https://github.com/hackforla/website/issues/2481

#### Used for creating this issue
- 1.01 Label name: P-Feature: Project Info and Page
- 1.01.01 Issue Tab: [P-Feature: Project Info and Page](https://github.com/hackforla/website/issues?q=is%3Aopen+label%3A%22P-Feature%3A+Project+Info+and+Page%22)
- 1.01.02 Project Board: [P-Feature: Project Info and Page](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=+label%3A%22P-Feature%3A+Project+Info+and+Page%22)
- 1.02 URL of page on Hack for LA website: A project's detail page (e.g. https://www.hackforla.org/projects/100-automations)
- 1.03 URL of link to code search: [repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// Project Info and Page](https://github.com/search?q=repo%3Ahackforla%2Fwebsite+NOT+language%3ASVG+NOT+path%3A%2F%5E_data%5C%2Finternal%5C%2Fcredits%5C%2F%2F+ProjectInfoAndPage&type=code)
- 1.04 URL of WIKI page: https://github.com/search?q=repo%3Ahackforla%2Fwebsite+Project+Info+and+Page&type=wikis
- 1.04.01 URL of future edits to wiki pages: https://github.com/hackforla/website/wiki/How-to-Contribute-to-the-Wiki (check this page to see if there are any other new edits in the queue.)
- 1.05 Issue for adding items to a final checklist: #8417

#### Created by this issue
- 2.01 [EXAMPLE would be a link to an issue related to delivering this page]
---
## Issues to write
### Must Have
TBD

### Should Have
TBD

### Could Have
TBD

---

last updated: 2026-08-18
Highest number found: 8737

## Relevance of the issues to the Homepage launch
### Must Have
- [ ] #7679
- why: This issue
- status: In progress (actively working)
- draft: False
- responsible: nadiaspn0503
- role: product

- [x] #8695
- why: Need to keep project information up to date
- status: New Issue Approval
- draft: True
- responsible: none
- role: back end/devOps and front end

- [ ] #8692
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8689
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8688
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8687
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8686
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8685
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8684
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8683
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8682
- why: Need to keep project information up to date
- status: New Issue Approval
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8681
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8680
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8679
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8678
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8676
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8675
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8674
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [ ] #8672
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [x] #8668
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: back end/devOps and front end

- [x] #8660
- why: Need to keep project information up to date
- status: Prioritized Backlog
- draft: False
- responsible: none
- role: back end/devOps and front end

- [x] #8659
- why: Need to keep project information up to date
- status: Prioritized Backlog
- draft: False
- responsible: none
- role: back end/devOps and front end

- [x] #8658
- why: Need to keep project information up to date
- status: Prioritized Backlog
- draft: False
- responsible: none
- role: back end/devOps and front end

- [x] #8657
- why: Need to keep project information up to date
- status: Prioritized Backlog
- draft: False
- responsible: none
- role: back end/devOps and front end

- [x] #8656
- why: Need to keep project information up to date
- status: Prioritized Backlog
- draft: False
- responsible: none
- role: back end/devOps and front end

- [x] #8655
- why: Need to keep project information up to date
- status: Prioritized Backlog
- draft: False
- responsible: none
- role: back end/devOps and front end

- [x] #8654
- why: Need to keep project information up to date
- status: Prioritized Backlog
- draft: False
- responsible: none
- role: back end/devOps and front end

- [x] #8543
- why: We need to create a template to create good first issues to populate the github-handle variable with the correct handle for each team member (excluding leadership team members).
- status: Ready for Prioritization
- draft: False
- responsible: None
- role: back end/devOps and front end

- [x] #8522
- why: Need to have Project Pages page with correct information.
- status: ERs and epics that are ready to be urned into issues
- draft: False
- responsible: None
- role: back end/devOps and front end

- [ ] #8407
- why: Need to ensure that text used across the projects follows consistent tone, terminology, and style conventions
- status: New Issue Approval
- draft: True
- responsible: kimberlyvaldez07
- role: product and writing

- [ ] #8054
- why: Need to have Project Pages page with correct information.
- status: New Issue Approval - LM 2025-09-17
- draft: True
- responsible: JessicaLucindaCheng
- role: dev leads, merge team, and product

- [ ] #6138
- why: To change the HfLA website code to read from as many repositories as specified per project
- status: In progress (actively working)
- draft: False
- responsible: JessicaLucindaCheng
- role: back end/devOps and front end

- [ ] #5127
- why: To update the languages for Access the Data so that visitors to the website can find accurate and up-to-date information.
- status: Ice box
- draft: False
- responsible: None
- role: back end/devOps and front end

- [ ] #4262
- why: To identify and update the technologies and tools requirement for all the projects.
- status: In progress (actively working)
- draft: False
- responsible: nadiaspn0503
- role: product
- [ ] #4153
- why: Move, refactor and add SDG info and images for the rollout plan.
- status: In progress (actively working)
- draft: False
- responsible: JessicaLucindaCheng
- role: Dev leads

- [ ] #2037
- why: To add information to each project md file to be displayed on the new Impact format.
- status: New Issue Approval
- draft: True
- responsible: None
- role: product

### Should Have
- [ ] #6277
- why: To reduce duplicate data
- status: In progress (actively working)
- draft: False
- responsible: JessicaLucindaCheng
- role: back end/devOps

- [ ] #6144
- why: Need to change the code for displaying contribution data for each person in a project that has 2 or more repositories (repos). This is used for the All-Time Contributors section of each project's detailed page.
- status: New Issue Approval
- draft: True
- responsible: JessicaLucindaCheng
- role: back end/devOps

- [ ] #5630
- why: Makes it easier to convert stakeholder requests into actionable developer issues.
- status: New Issue Approval
- draft: True
- responsible: JessicaLucindaCheng
- role: back end/devOps and front end

### Could Have
List of all could have issues

- #8428
- why: Create issues to populate the github-handle variable with the correct handle for each member of the leadership team
- status: In progress (actively working)
- draft: False
- responsible: kdaca19xx and xnealcarson
- role: back end/devOps and front end

- #7801
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7799
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7795
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7794
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7781
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7765
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7764
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7763
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7435
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7434
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7432
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7431
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7430
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7401
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7384
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #7102
- why: Create a single variable to hold a GitHub handle
- status: Prioritized backlog
- draft: False
- responsible: None
- role: back end/devOps and front end

- #6820
- why: Dates needed for the future but are not currently needed.
- status: ERs and epics that are ready to be turned into issues
- draft: False
- responsible: None
- role: back end/devOps

- #6819
- why: To reduce scattered information and solve an emerging problem
- status: Ice box
- draft: True
- responsible: ExperimentsInHonesty
- role: back end/devOps

- #6321
- why: To make it easy for future team members to edit.
- status: Ice box
- draft: False
- responsible: None
- role: front end

- #6139
- why: To update the languages for Access the Data for website users to find accurate and up-to-date information
- status: In progress (actively working)
- draft: False
- responsible: JessicaLucindaCheng
- role: back end/devOps and front end

- #6017
- why: Ensures meetings display correctly on Project pages
- status: New Issue Approval
- draft: True
- responsible: None
- role: back end/devOps

- #5441
- why: Create a single variable to hold a GitHub handle
- status: In progress (actively working)
- draft: False
- responsible: daras-cu
- role: back end/devOps and front end

- #5440
- why: Create a single variable to hold a GitHub handle
- status: Ice box
- draft: False
- responsible: None
- role: back end/devOps

- #312
- why: Provide collateral for the HackforLA website
- status: New Issue Approval
- draft: False
- responsible: None
- role: product

### Won't have this time
List of all won't have issues

- #7726
- #4342
- #3526

#### Templates
```
- [ ] #
- why:
- status:
- draft:
- responsible:
- role:
```
```
### Issues list associated with this epic
last updated:
Highest number found:
```

List of all issue by number

- #8695
- #8692
- #8689
- #8688
- #8687
- #8686
- #8685
- #8684
- #8683
- #8682
- #8681
- #8680
- #8679
- #8678
- #8676
- #8675
- #8674
- #8672
- #8668
- #8660
- #8659
- #8658
- #8657
- #8656
- #8655
- #8654
- #8543
- #8522
- #8428
- #8407
- #8054
- #7801
- #7799
- #7795
- #7794
- #7781
- #7765
- #7764
- #7763
- #7726
- #7679
- #7435
- #7434
- #7432
- #7431
- #7430
- #7401
- #7384
- #7102
- #6820
- #6819
- #6321
- #6277
- #6144
- #6139
- #6138
- #6017
- #5630
- #5441
- #5440
- #5127
- #4342
- #4262
- #4153
- #3526
- #2037
- #312