EPIC: Prepare the entire site (issues that are on many pages) for Homepage Launch

[priyanka02art]

Overview

We need to track existing issues and make new issues to deliver entire site (issues that are on many pages) 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 names
  • feature: branding
  • feature: spelling
  • P-Feature: Navigation
  • 1.01.01 Issue Tab: label:"feature: branding","feature: spelling","P-Feature: Navigation"
  • 1.01.02 Project Board: label:"feature: branding","feature: spelling","P-Feature: Navigation"
• 1.02 URL of page on Hack for LA website: see every page on the site
• 1.03 URL of link to code search: repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// branding, repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// spelling, repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// Navigation
• 1.04 URL of WIKI page: https://github.com/search?q=repo%3Ahackforla%2Fwebsite+Navigation&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: 2026-03-04
Highest number found: 8539

Relevance of the issues to the Homepage launch

Must Have

• EPIC: Prepare the entire site (issues that are on many pages) for Homepage Launch #7680

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

• EPIC: Prepare the Header and Footer navigation for Homepage Launch #7678

  • why: We need to track existing issues and make new issues to deliver Header and Footer navigation complete enough for the Homepage launch.
  • status: New Issue Approval
    • draft: True
    • responsible: kimberlyvaldez07
  • role: Product

• Correct Comma in Project Meetings Page #8539

  • why: Our website needs to use the comma consistently so that the website is correct and uniform. In this issue we will be changing text on the Project Meetings page.
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: back end/devOps and front end

• Correct Comma in Site Map Page #8514

  • why: Our website needs to use the comma consistently so that the website is correct and uniform. In this issue we will be changing text on the Site Map page.
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: Back end/devOps and front end

• Correct Oxford Comma in Join Us Page #8513

  • why: Our website needs to use the Oxford comma consistently so that the website is correct and uniform. In this issue we will be changing text on the Join Us page.
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: Back end/devOps and front end

• Correct Oxford Comma in Join Us Page #8512

  • why: Our website needs to use the Oxford comma consistently so that the website is correct and uniform. In this issue we will be changing text on the Join Us page.
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: Back end/devOps and front end

• Correct Oxford Comma in Communities of Practice Page #8511

  • why: Our website needs to use the Oxford comma consistently so that the website is correct and uniform. In this issue we will be changing text on the Communities of Practice page.
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: Back end/devOps and front end

• Correct Oxford Comma in Projects Page #8510

  • why: Our website needs to use the Oxford comma consistently so that the website is correct and uniform. In this issue we will be changing text on the Project Page.
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: Back end/devOps and front end

• Epic: Fix Oxford Comma Across Website for Homepage Launch #8482

  • why: We need to make sure the Oxford comma is in the correct spots across the entire website for consistency.
  • status: New Issue Approval
    • draft: True
    • responsible: none
  • role: Front end and product

• ER: Find all the places that Github should be GitHub and fix #6161

  • why: Maintaining proper spelling and capitalization is important for both professionalism and consistency. Public-facing content should be free of errors to uphold credibility, while internal code should follow best practices for clarity. For example, "GitHub" is a company name and should be capitalized, except when used in URLs, variables, or directory names—where lowercase (e.g., github) is standard due to naming conventions.
  • status: In Progress (actively working)
    • draft: False
    • responsible: daras-cu
  • role: Back End/devOps and front end

• Develop GHA for spell checking PRs #5334

  • why: We need a GHA to scan the files changed in Pull Requests using the Code Spell Checker CLI, in order to ensure that no misspellings are posted on the website.
  • status: Ice Box
    • draft: True
    • responsible: None
  • role: Back End/ DevOps

• Epic: Create issues to add false positives to cspell.json #5312

  • why: To avoid repeatedly flagging false positives, we need to update the Code Spell Checker config file. These entries are tracked in the HfLA spelling audit spreadsheet, which will also be used for issue tracking.
  • status: New issue approval
    • draft: False
    • responsible: none
  • role: Back end/devOps and front end

• Epic: Create template, spreadsheet and list of issues for spellcheck audit #5248

  • why: We need to create issues to audit all appropriate codebase files for Code Spell Checker results. The HfLA spelling audit spreadsheet1 will be used to track spell check audit issues, record false positives and misspellings, and track resulting issues for resolving errors.
  • status: new issue approval
    • draft: False
    • responsible: None
  • role: Backend/devOps

• Create mobile version of new top nav  #2513

  • why: create a mobile version of the new top nav bar so that it can be implemented and launched alongside the desktop version.
  • status: ice box
    • draft: false
    • responsible: none
  • role: design

Should Have

• Research URL trailing slash removal for issue creation #8457

  • why: We need to research how to remove trailing slashes from all hackforla.org page URLs
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: Front end

• Create issue template "Resolve Spell Check warning" #6446

  • why: We need a template for reporting spell check warnings, so that we can create issues to address.
  • status: Ice Box
    • draft: False
    • responsible: None
  • role: Back End/ DevOps

• Update PR template with instructions regarding spell check messages #5202

  • why: We need to direct developers how to manage spell check messages on changed files locally, and also those that may appear in Pull Request checks.
  • status: Ice Box
    • draft: True
    • responsible: None
  • role: Dev Leads

• Create a Roll Out Plan for adding Code Spell Checker VS Code Extension #4349

  • why: create a roll out plan for having all HfLA website developers install the Code Spell Checker VS Code extension so that we can reduce confusion for our dev team
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: back end/devOps and dev leads

• Add ESlint VS Code installation instructions #4264

  • why: add installation instructions for the VS Code extension, ESLint, so our developers will be aligned on the local spellchecker used.
  • status: ice box
    • draft: false
    • responsible: None
  • role: back end/devOps

• Moderated Usability Test for the top navigation design (mobile) #2686

  • why: perform usability testing to assess the functionality of the top nav menu (mobile).
  • status: new issue approval
    • draft: True
    • responsible: none
  • role: user research

Could Have

List of all could have issues

• Designing a virtual Zoom background #3191

  • why: When we present our organization to stakeholders and interviewers, we need a professional and dynamic Zoom background that represents HFLA.
  • status: new issue approval
    • draft: false
    • responsible: none
  • role: design

• Schedule Brand Sprint #609

  • why: we need to take a step back and think about our brand identity.
  • status: ice box
    • draft: false
    • responsible: none
  • role: product

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

• Correct Comma in Project Meetings Page #8539
• Correct Comma in Site Map Page #8514
• Correct Oxford Comma in Join Us Page #8513
• Correct Oxford Comma in Join Us Page #8512
• Correct Oxford Comma in Communities of Practice Page #8511
• Correct Oxford Comma in Projects Page #8510
• Epic: Fix Oxford Comma Across Website for Homepage Launch #8482
• Research URL trailing slash removal for issue creation #8457
• EPIC: Prepare the entire site (issues that are on many pages) for Homepage Launch #7680
• EPIC: Prepare the Header and Footer navigation for Homepage Launch #7678
• Create issue template "Resolve Spell Check warning" #6446
• ER: Find all the places that Github should be GitHub and fix #6161
• Develop GHA for spell checking PRs #5334
• Epic: Create issues to add false positives to cspell.json #5312
• Epic: Create template, spreadsheet and list of issues for spellcheck audit #5248
• Update PR template with instructions regarding spell check messages #5202
• Create a Roll Out Plan for adding Code Spell Checker VS Code Extension #4349
• Add ESlint VS Code installation instructions #4264
• Designing a virtual Zoom background #3191
• Moderated Usability Test for the top navigation design (mobile) #2686
• Create mobile version of new top nav  #2513
• Schedule Brand Sprint #609

[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