EPIC: Prepare the Toolkit page for Homepage Launch
- 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 Toolkit 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.
- [ ] 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: Toolkit
- 1.01.01 Issue Tab: [P-Feature: Toolkit ](https://github.com/hackforla/website/issues?q=is%3Aopen%20label%3A%22P-Feature%3A%20Toolkit%22%20)
- 1.01.02 Project Board: [P-Feature: Toolkit](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=+label%3A%22P-Feature%3A+Toolkit%22)
- 1.02 URL of page on Hack for LA website: https://www.hackforla.org/toolkit/
- 1.03 URL of link to code search: [repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// TOOLKIT](https://github.com/search?q=repo%3Ahackforla%2Fwebsite+NOT+language%3ASVG+NOT+path%3A%2F%5E_data%5C%2Finternal%5C%2Fcredits%5C%2F%2F+TOOLKIT&type=code)
- 1.04 URL of WIKI page: https://github.com/search?q=repo%3Ahackforla%2Fwebsite+TOOLKIT&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: Once homepage launch is ready evaluate if the toolkit page needs to be temporarily removed based on lack of viable content.
### Should Have
TBD
### Could Have
TBD
---
last updated: 2026-08-18
Highest number found: 8558
## Relevance of the toolkit issues to the Homepage launch
### Must Have
- [ ] #7675
- why: It is the epic for this page (this issue)
- status: New Issue Approval
- draft: True
- responsible: kimberlyvaldez07
- role: Product
- [ ] #6161
- why: GitHub is a company name and should only be in lowercase (github) when in a URL, variable or directory name
- status: In Progress (actively working)
- draft: False
- responsible: daras-cu
- role: Back end/devOps and front end
- [ ] #3889
- why: We need to make the Scalable Vector Graphics (SVGs) in the Toolkit webpage's External Resources section Web Content Accessibility Guidelines (WCAG) compliant so that we can achieve our mission of inclusivity.
- status: Ice Box
- draft: False
- responsible: None
- role: Front End
- [ ] #1848
- why: Ensure all website pages function correctly on mobile by identifying and fixing any mobile-specific bugs.
- status: Ice Box
- draft: False
- responsible: None
- role: Design
### Should Have
- [ ] #8558
- why: We need to add filtering functionality to the Toolkit page so that selected filters are applied to the External Resources cards in addition to the Guide Pages cards.
- status: Ready for Prioritization
- draft: False
- responsible: None
- role: Back end/devOps
- [ ] #1515
- why: We need to create a mobile version to ensure the code is responsive across all screen sizes.
- status: Ice Box
- draft: False
- responsible: None
- role: Front End
### Could Have
List of all could have issues
- #6673
- why: This CodeQL alert is a false positive and is only being left open so that we can test a solution for eliminating false positives. Dependencies-#6548
- 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
- #3528
- why: Ensure consistent text elements on the Toolkit page
- status: Ice Box
- draft: False
- responsible: None
- role: Design
- #3356
- why: We want to add a new external resource to the website toolkit
- status: Ice Box
- draft: True
- responsible: None
- role: Front End
- #918
- why: This information is already missing from the site with the Toolkit visible so it won't make a difference once we launch the homepage. If we do add it, it will be because we need to add the following details to the Guide on [Getting the Most Out of GitHub Issues](https://www.hackforla.org/guide-pages/github-issues.html) to enable a more comprehensive understanding for new volunteers
- status: Ice Box
- draft: True
- responsible: None
- role: Product
### Won't have this time
List of all won't have issues
- #3115
#### Template
```
- [ ] #
- why:
- status:
- draft:
- responsible:
- role:
```
```
### Issues list associated with this epic
last updated:
Highest number found:
```
List of all issue by number
- #8558
- #7675
- #6673
- #6161
- #6143
- #3889
- #3528
- #3356
- #3115
- #1848
- #1515
- #918
Contributor guide
Assessment
This issue has not been assessed yet.