EPIC: Prepare the Header and Footer navigation for Homepage Launch

[priyanka02art]

Overview

We need to track existing issues and make new issues to deliver Header and Footer navigation 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

Desktop Width of 1440px

Header

Full Header

Our Work

Join Us

Get in Touch

Toolkit

Footer

Footer

---

Tablet Width of 768px

Header

Full Header

Our Work

Join Us

Get in Touch

Toolkit

Footer

Footer

---

Mobile Width of 480px

Header

Menu Collapsed

Menu Expanded

Footer

Footer

---

• Parent Epic: Initiative: homepage launch #2481

Used for creating this issue

• 1.01 Label names: P-Features: Footer, P-Feature: Navigation
  • 1.01.01 Issue Tab: P-Feature: Footer,P-Feature: Navigation
  • 1.01.02 Project Board: P-Feature: Footer,P-Feature: Navigation
• 1.02 URL of page on Hack for LA website: see any page
• 1.03 URL of link to code search: repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// Navigation repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// footer
• 1.04 URL of WIKI page: https://github.com/search?q=repo%3Ahackforla%2Fwebsite+Navigation&type=wikis, https://github.com/search?q=repo%3Ahackforla%2Fwebsite+footer&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-04-21
Highest number found: 7680

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 Homepage launch
  • status: New Issue Approval
    • draft: True
    • responsible: kimberlyvaldez07
  • role: Product

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

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

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

  • why: Lists all the placed where github needs to be replaced with GitHub so that we display the company name correctly
  • status: In Progress (actively working)
    • draft: False
    • responsible: daras-cu
  • role: Back end/devOps and front end

• Create mobile version of new top nav  #2513

  • why: We need to 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

• Moderated Usability Test for the top navigation design (mobile) #2686
  • why: We want to ensure that mobile users will be able to access website content using the accordion style navigation design
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: User Research

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

• 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
• ER: Find all the places that Github should be GitHub and fix #6161
• Moderated Usability Test for the top navigation design (mobile) #2686
• Create mobile version of new top nav  #2513

[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