EPIC: Prepare the Events page for Homepage Launch

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

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

- [ ] #8433
- why: We need to replace the Happy Hour section with a Summer Meetup to keep the website up to date.
- status: Ready for Prioritization
- draft: False
- responsible: none
- role: Front end, product, and writing

- [ ] #8432
- why: We are no longer an in person organization and have moved remote.
- status: Ice box
- draft: True
- responsible: None
- role: back end/dev Ops and front end

- [ ] #8431
- why: we can move this information to the About page to highlight that we were an active in person organization that moved remote
- status: Ready for Prioritization
- draft: False
- responsible: None
- role: back end/dev Ops and front end

### Should Have

### Could Have
List of all could have issues

- #6321
- why: We need to add info to the wiki under the pages details, that make it easy for future team members to edit and know which pages use which files.
- status: Ice Box
- draft: False
- responsible: None
- role: Front End

- #3289
- why: Ensure consistent text elements on the Events page
- status: New Issue Approval
- draft: False
- responsible: None
- role: Design

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

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

List of all issue by number

- #8433
- #8432
- #8431
- #7674
- #6321
- #3289