EPIC: Prepare the Join Us page for Homepage Launch

[priyanka02art]

Overview

We need to track existing issues and make new issues to deliver Join Us 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: Join Page
  • 1.01.01 Issue Tab: P-Feature: Join Page
  • 1.01.02 Project Board: P-Feature: Join Page
• 1.02 URL of page on Hack for LA website: https://www.hackforla.org/join
• 1.03 URL of link to code: repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// Join us
• 1.04 URL of WIKI page: https://github.com/search?q=repo%3Ahackforla%2Fwebsite+Join+Page&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: 8513

Relevance of the issues to the Homepage launch

Must Have

• EPIC: Prepare the Join Us page for Homepage Launch #7672

  • why: It is the epic for this page (this issue)
  • status: In progress (actively working)
    • draft: False
    • responsible: nadiaspn0503
  • role: Product

• 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: False
    • 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: False
    • responsible: None
  • role: Back end/devOps and front end

• ER: create new page for joining the admin team #6833

  • why: The admin meeting times appear on the events page, but the link does not lead to relevant information. Temporary fix is to direct it to the Join Us page, but a dedicated section for joining the admin team should be added in the future.
  • status: Emergent Requests
    • draft: True
    • responsible: None
  • role: Design

Should Have

• ER: Headers Are Different Heights From the Top Navigation Bar in Mobile Views #7510
  • why: The Donate page header and the Join Us header are different heights from the navigation bar at the top of the page in mobile and tablet views
  • status: New Issue Approval
    • draft: True
    • responsible: JessicaLucindaCheng
  • role: Back end/devOps and front end

Could Have

List of all could have issues

• Design System Audit: Text Elements: Join Us Page #3525
  • why: Ensure consistent text elements on the Join Us page
  • status: Prioritized Backlog
    • draft: False
    • responsible: None
  • role: Design

Won't have this time

List of all won't have issues

• Administer UX interview forms to organizational stakeholders #186

Templates

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

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

List of all issue by number

• Correct Oxford Comma in Join Us Page #8513
• Correct Oxford Comma in Join Us Page #8512
• EPIC: Prepare the Join Us page for Homepage Launch #7672
• ER: Headers Are Different Heights From the Top Navigation Bar in Mobile Views #7510
• ER: create new page for joining the admin team #6833
• Design System Audit: Text Elements: Join Us Page #3525
• Administer UX interview forms to organizational stakeholders #186

[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

[priyanka02art]

• Join Us page: Add anchors to sections Advise Us, Volunteer with Us, and Partner with Us #3026
• Join us page Issues on the project board
  URL: https://www.hackforla.org/join
  ER: Fix text alignment on Join Us and About header #5973