EPIC: Prepare the Wins page and wins card randomizer for Homepage Launch

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

---
## Relevance of the issues to the Homepage launch
last updated: 2026-08-18
Highest number found: 8701

### Must Have
- [ ] #7664
- why: It is the epic for this page (this issue)
- status: New Issue Approval
- draft: True
- responsible: kimberlyvaldez07
- role: product

- [ ] #8701
- why: We need to update the Wins Google Apps scripts so that it starts adding issues from the old project board to the new project board's "Questions/In Review" column.
- status: In progress (actively working)
- draft: False
- responsible: castillios
- role: Back en/devOps

- [ ] #8492
- why: We need to change the WINS form to only offer to use their GitHub image. We will not be able to display people's LinkedIn profile pictures so we need to revise the form to reflect that.
- status: New Issue Approval
- draft: True
- responsible: daras-cu
- role: Front end

### Should Have
- [ ] #8493
- why: We need to ask people to submit wins to add to the wins page.
- status: Ready for Prioritization
- draft: False
- responsible: None
- role: Product and writing

- [ ] #7707
- why: Once the site is re launched, if we discover a problem during usability testing, we want to be able to fix things fast and this script is notoriously hard for new people to work on.
- status: Questions / In Review
- draft: False
- responsible: daras-cu
- role: back end/devOps

- [ ] #6668
- why: Requires review to determine action. See https://github.com/hackforla/website/issues/6668#issuecomment-3229775578 (ready for dev lead and added to the [dev/pm agenda 2025-08-25](https://github.com/hackforla/website/issues/7859#issuecomment-3221706808) for adding to 2025-09-08
- status: Ready for Prioritization
- draft: False
- responsible: None
- role: front end

- [ ] #4388
- why: so that post launch we know how people interacted with this page
- status: ERs and epics that are ready to be turned into issues
- draft: False
- responsible: None
- role: backend/devOps

- [ ] #3145
- why: social media strategy for announcing launch
- status: ice box
- draft: True
- responsible: None
- role: product

- [ ] #3142
- why: to create a better use experience that has them share it with other people
- status: New Issue Approval
- draft: True
- responsible: None
- role: product

- [ ] #3140
- why: to get more people to complete their wins submissions (instead of dropping out)
- status: prioritized backlog
- draft: False
- responsible: None
- role: writing

### Could Have
List of all could have issues

- #6672
- why: Is dependent on a different issue being solved and is likely a false positive.
- status: Ice box
- draft: False
- responsible: None
- role: front end

- #2148
- why: Its technical debt and not crucial to the launch, but if we want to change anything about the wins card, or do dynamic card on the about page (which we removed from launch requirement), we will need this issue done.
- status: Ice box
- draft: False
- responsible: None
- role: back end/devOps

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

- #4671
- #3627
- #3529
- #3143

#### Template
```
- [ ] #
- why:
- status:
- draft:
- responsible:
- role:
```
List of all issue

- #8701
- #8493
- #8492
- #7707
- #7664
- #6672
- #6668
- #4671
- #4388
- #3627
- #3529
- #3145
- #3143
- #3142
- #3140
- #2148