EPIC: Prepare the Dashboard page for Homepage Launch

[priyanka02art]

Overview

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

Relevance of the issues to the Homepage launch

Must Have

• EPIC: Prepare the Dashboard page for Homepage Launch #7667
  • why: It is the epic for this page (this issue)
  • status: New Issue Approval
    • draft: True
    • responsible: nadiaspn0503
  • role: Product

If we do have the could have done by the time homepage is ready to launch then create a new issue to hind the metrics section on about page.

Should Have

Could Have

List of all could have issues

• Requirements for the Org Dashboard #7725

  • why: It lists all requirements for the Org Dashboard to ensure clear priorities, resource allocation, and effective management as we move forward with development.
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: Product

• Epic: Org Dashboard #7506

  • why: Manage the work for Org dashboard to prioritize and recruit.
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: Product

• ER: Fix dashboard data script (workflow) #6229

  • why: To detect when the dashboard data script fails
  • status: New Issue Approval
    • draft: True
    • responsible: ExperimentsInHonesty
  • role: backend/DevOps

Won't have this time

List of all won't have issues

• Initiative: Dashboards planning #6614
• ER: Add analytics about how many people we reach to the Dashboard #4537
• Website User Behavior Modeling - current visitor data gathering #128

Templates

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

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

List of all issue by number

• Requirements for the Org Dashboard #7725
• EPIC: Prepare the Dashboard page for Homepage Launch #7667
• Epic: Org Dashboard #7506
• Initiative: Dashboards planning #6614
• ER: Fix dashboard data script (workflow) #6229
• ER: Add analytics about how many people we reach to the Dashboard #4537
• Website User Behavior Modeling - current visitor data gathering #128

[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