hackforla / hackforla/website

EPIC: Prepare the About Us, Accomplishment Section for Homepage Launch

Open
#7,663 6 comments 0 reactions 1 assignee Claimed by @nadiaspn0503 View on GitHub
Complexity: Medium Draft epic HLC: M Homepage Launch Countdown p-feature: accomplishments role: product size: 1pt
Dominant language
JavaScript
Stars
363
Forks
872
Avg merge
2d 21h
Merged PRs (30d)
18

Description

### Overview
We need to track existing issues and make new issues to deliver About Us, Accomplishment Section 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`
- [ ] 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
- [ ] 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.
- [ ] Make the issues specified
- [ ] Link them as sub issues to this issue
- [ ] 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: accomplishments](https://github.com/hackforla/website/labels/p-feature%3A%20accomplishments)
- 1.02 URL of page on Hack for LA website: https://www.hackforla.org/about/#accomplishments
- 1.03 URL of link to code search: [repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// accomplishments](https://github.com/search?q=repo%3Ahackforla%2Fwebsite+NOT+language%3ASVG+NOT+path%3A%2F%5E_data%5C%2Finternal%5C%2Fcredits%5C%2F%2F+accomplishments&type=code)
- https://github.com/hackforla/website/blob/gh-pages/_data/internal/accomplishments.yml (has the 2020 content in it)
- https://github.com/hackforla/website/blob/gh-pages/_includes/about-page/about-card-accomplishments.html controls how it appears in the accomplishments section
- 1.04 URL of WIKI page: https://github.com/search?q=repo%3Ahackforla%2Fwebsite+accomplishments&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: 8628

## Relevance of the issues to the Homepage launch
### Must Have
- [ ] #7663
- why: It is the epic for this page (this issue)
- status: New Issue Approval
- draft: True
- responsible: nadiaspn0503
- role: Product

- [ ] #8628
- why: The purpose is to use the newly made form template that's associated with the issue in the linked dependency, to add each year's accomplishments summary for the Guides Team.
- status: Ice Box
- draft: True
- responsible: None
- role: Front end

- [ ] #8476
- why: We need a new issue form template that will allow project teams add or revise an accomplishment for a specified year.
- status: Ready for Prioritization
- draft: False
- responsible: None
- role: Front end

- [ ] #7578
- why: We need to write brief summaries of project accomplishments for each year of the project's life, to go on the website's accomplishments page.
- status: New Issue Approval
- draft: True
- responsible: None
- role: Project

### Should Have

### Could Have
List of all could have issues

### 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

- #8628
- #8476
- #7663
- #7578

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.