EPIC: Prepare the Projects page for Homepage Launch

### Overview
We need to track existing issues and make new issues to deliver Projects 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: Projects page
- 1.01.01 Issue Tab: [P-Feature: Projects page](https://github.com/hackforla/website/labels/P-Feature%3A%20Projects%20page)
- 1.01.02 Project Board: [P-Feature: Projects Page](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=label%3A%22P-Feature%3A+Projects+page%22+)
- 1.02 URL of page on Hack for LA website: https://www.hackforla.org/projects/
- 1.03 URL of link to code search: [repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// projects](https://github.com/search?q=repo%3Ahackforla%2Fwebsite+NOT+language%3ASVG+NOT+path%3A%2F%5E_data%5C%2Finternal%5C%2Fcredits%5C%2F%2F+projects&type=code)
- 1.04 URL of WIKI page: https://github.com/search?q=repo%3Ahackforla%2Fwebsite+projects&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: 8711

## Relevance of the issues to the Homepage launch
### Must Have
- [ ] #7666
- why: It is the epic for this page (this issue)
- status: In Progress (actively working)
- draft: True
- responsible: priyanka02art and nadiaspn0503
- role: Product

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

- [ ] #8702
- why: Need to keep project information up to date
- status: Ready for Prioritization
- draft: False
- 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

- [ ] #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: In progress (actively working)
- draft: False
- responsible: Tomomi-K1
- role: back end/devOps and front end

- [x] #8658
- why: Need to keep project information up to date
- status: In progress (actively working)
- draft: False
- responsible: palak-hellowrld
- role: back end/devOps and front end

- [x] #8657
- 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] #8656
- why: Need to keep project information up to date
- status: In progress (actively working)
- draft: False
- responsible: KyleA99
- role: back end/devOps and front end

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

- [ ] #8624
- why: We need to ignore Dockerfile as a language so that projects on the projects page are accurately displayed.
- status: Ice Box
- draft: False
- responsible: None
- role: Front end

- [x] #8623
- why: We need to add docker to the list of technologies for teams with dockerfile listed as a language so that the technologies list of each team is up-to-date.
- status: In progress (actively working)
- draft: False
- responsible: none
- role: Front end

- [x] #8507
- why: We need to correctly classify tools and technologies used in projects so users/volunteers have clarity on what systems are being used.
- status: In progress (actively working)
- draft: False
- responsible: jjam02 and sushma110396
- role: Front end

- [ ] #8467
- why: We need to integrate the search bar with the filter system so that search terms update the filter counter, provide immediate visual feedback, and allow users to continuously add multiple search terms.
- status: Ready for Prioritization
- draft: False
- responsible: None
- role: back end/devOps and front end

- [ ] #8466
- why: We need to fix the mobile view search behavior so that the page maintains its scroll position and the filter bar remains open after a user performs a search.
- status: Ready for Prioritization
- draft: False
- responsible: None
- role: Front end

- [x] #8170
- why: The link to the Test Site for TDM Calculator on the project page is incorrect.
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: front end

- [ ] #8054
- why: Helps PMs and leads know what to do with "Update Project Profile" ERs or epics with sub-issue(s) that have already been written
- status: New Issue Approval
- draft: True
- responsible: JessicaLucindaCheng
- role: dev leads, merge team, and product

- [ ] #4434
- why: We need to make sure that languages are not being added to tools and technologies fields on project.md cards and that items that should be in tools are not in technologies and vice versa
- status: Ice Box
- draft: False
- responsible: None
- role: Dev leads and Product

- [ ] #4262
- why: Ensure users receive accurate and relevant information to navigate seamlessly between projects.
- status: In progress (actively working)
- draft: False
- responsible: nadiaspn0503
- role: Product

### Should Have
- #6138
- why: without this projects that have more than one repo, will only have their primary repo show up on the project's page and their project info page
- status: In Progress (actively working)
- draft: False
- responsible: JessicaLucindaCheng
- role: Back end/DevOps and front end

### Could Have
List of all could have issues

- #8490
- why: Potentially we could remove the completed projects to an archived section unless we want to keep them on the site for visibility.
- status: Ready for Prioritization
- draft: False
- responsible: None
- role: back end/devOps and front end

- #6675 - this issue might get resolved before we launch but it's not required.
- why: There seems to be an incorrect alert but not sure what action triggers the alert. need more clarity ExperimentsInHonesty
- status: Ice Box
- draft: False
- responsible: None
- role: Front End

- #6143
- why: To enhance user experience, add a "List View" button on the Projects and Toolkit pages for a more concise presentation of information.
- status: Ice Box
- draft: True
- responsible: None
- role: Front End

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

- #6819

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

List of all issue by number

- #8692
- #8672
- #8668
- #8660
- #8658
- #8657
- #8656
- #8655
- #8624
- #8623
- #8507
- #8490
- #8467
- #8466
- #8170
- #8054
- #7666
- #6819
- #6675
- #6143
- #6138
- #4434
- #4262