EPIC: Prepare the Toolkit page for Homepage Launch

[priyanka02art]

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

• List all the issues related to the label
• 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
• 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]
  

• 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: Initiative: homepage launch #2481

Used for creating this issue

• 1.01 Label name: P-Feature: Toolkit
  • 1.01.01 Issue Tab: P-Feature: Toolkit
  • 1.01.02 Project Board: P-Feature: Toolkit
• 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
• 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: Product: Final checks for Homepage Launch #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: 2025-12-16
Highest number found: 7675

Relevance of the toolkit issues to the Homepage launch

Must Have

• EPIC: Prepare the Toolkit page for Homepage Launch #7675

  • why: It is the epic for this page (this issue)
  • status: New Issue Approval
    • draft: True
    • responsible: kimberlyvaldez07
  • role: Product

• Replace Github with GitHub in _guide-pages/2FA.html #7418

  • why: We need to replace instances of Github and github with GitHub so that we display the company name correctly.
  • status: Prioritized Backlog
    • draft: False
    • responsible: None
  • role: Front End

• ER: Find all the places that Github should be GitHub and fix #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

• Toolkit page: Make the External Resources section cards' SVGs WCAG compliant #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

Should Have

• Resolve CodeQL Alert #33 - Generated by GHA #6673 (not clear on what the error is)

  • why: We need to resolve the new alert (33) and either recommend dismissal of the alert or update the code files to resolve the alert.
  • status: Ice Box
    • draft: False
    • responsible: None
  • role: Front end

• Mobile Responsiveness on toolkit #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

• Create mobile version of the Guide Pages and ensure responsiveness #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

• Add hash URL navigation on /toolkit/ page #7668

  • why: URL consistency and hash navigation are broken as the hash is removed, preventing anchor link jumps.
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Resolve CodeQL Alert #33 - Generated by GHA #6673 (not clear on what the error is)

  • 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-Update codeql.yml to exclude YAML front-matter and Liquid code #6548
  • status: Ice Box
    • draft: False
    • responsible: None
  • role: Front end

• Create "List" view on Project and Toolkit pages #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

• Design System Audit: Text Elements: Toolkit Page #3528

  • why: Ensure consistent text elements on the Toolkit page
  • status: Ice Box
    • draft: False
    • responsible: None
  • role: Design

• Add this resource to the ToolKit External Resources section #3356 (not clear on what the issue)

  • why: We want to add a new external resource to the website toolkit
  • status: Ice Box
    • draft: True
    • responsible: None
  • role: Front End

• Mobile Responsiveness on toolkit #1848

  • why: This mobile responsiveness is specifically for when the published guides have sticky navs, and currently none of the published guides appearing on the toolkit have them. Dependencies Create mobile version of the Guide Pages and ensure responsiveness #1515 Guide Pages - Sticky Navigation Fix #3170
    • draft: False
    • responsible: None
  • role: Design

• Adding 'Label' Information to the Guide on Getting the Most Out of GitHub Issues #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 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

• Requirements Gathering for 'Suggest a Guide' Button Link on Toolkits Page #3115
• Add this resource to the ToolKit External Resources section #3356

Template

- [ ] #
   - why: 
   - status: 
      - draft: 
      - responsible: 
   - role:  

### Issues list associated with this epic
last updated: 
Highest number found:

List of all issue by number

• EPIC: Prepare the Toolkit page for Homepage Launch #7675
• Add hash URL navigation on /toolkit/ page #7668
• Replace Github with GitHub in _guide-pages/2FA.html #7418
• Resolve CodeQL Alert #33 - Generated by GHA #6673
• ER: Find all the places that Github should be GitHub and fix #6161
• Create "List" view on Project and Toolkit pages #6143
• Toolkit page: Make the External Resources section cards' SVGs WCAG compliant #3889
• Design System Audit: Text Elements: Toolkit Page #3528
• Add this resource to the ToolKit External Resources section #3356
• Requirements Gathering for 'Suggest a Guide' Button Link on Toolkits Page #3115
• Mobile Responsiveness on toolkit #1848
• Create mobile version of the Guide Pages and ensure responsiveness #1515
• Adding 'Label' Information to the Guide on Getting the Most Out of GitHub Issues #918

[github-actions]

Hi @priyanka02art.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:

• Complexity, Role, Feature, Size

NOTE: Please ignore this comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels