EPIC: Prepare the Wins page and wins card randomizer for Homepage Launch

[priyanka02art]

Overview

We need to track existing issues and make new issues to deliver Wins 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: Wins Page
  • 1.01.01 Issue Tab: P-Feature: Wins Page
  • 1.01.02 Project Board: P-Feature: Wins Page
• 1.02 URL of page on Hack for LA website: https://www.hackforla.org/wins/
• 1.03 URL of link to code search: repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// wins
• 1.04 URL of WIKI page: https://github.com/hackforla/website/wiki/Wins-page
  • 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.04.01.01 Create wiki page "Hfla Google Apps Script Development/Review Process" #4134 (comment)
    • 1.04.01.02Create wiki page providing guidance how to test the WINS page #6680 (comment)
• 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

• Manually pick a new win, and hard code it on the about page. The randomizer can't get worked on until the homepage branch is merged into the gh-pages branch
• change the WINS form to only offer to use their GitHub image. We will not be able to display people's LinkedIn profile pictures, the LinkedIn API Terms of Service disallows it. So we need to revise the form to reflect that.

Should Have

• ask people to submit wins

---

Relevance of the issues to the Homepage launch

last updated: 2025-12-16
Highest number found: 8427

Must Have

• EPIC: Prepare the Wins page and wins card randomizer for Homepage Launch #7664

  • why: This EPIC
  • status: New Issue Approval
    • draft: True
    • responsible: kimberlyvaldez07
  • role: product

• Review Needed - New Wins Form Submission #8427

  • why: New wins form submission must be reviewed
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: Product

• Review Needed - New Wins Form Submission #8426

  • why: New wins form submission must be reviewed
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: Product

• Review Needed - New Wins Form Submission #8280

  • why: New wins form submission must be reviewed
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: Product

• Review Needed - New Wins Form Submission #8279

  • why: New wins form submission must be reviewed
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: Product

• Review Needed - New Wins Form Submission #8145

  • why: New wins form submission must be reviewed
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: Product

• ER: Issues to examine new wins data will be posted to the old project board #7594

  • why: if wins don't show up in the new project board, they won't be reviewed and added to the site
  • status: new issue approval
    • draft: True
    • responsible: none
  • role: backend/devOps

Should Have

• Update documentation for wins_data #7707

  • why: Once the site is re launched, if we discover a problem during usability testing, we want to be able to fix things fast and this script is notoriously hard for new people to work on.
  • status: Questions / In Review
    • draft: False
    • responsible: daras-cu
  • role: back end/devOps

• Resolve CodeQL Alert #49 in wins-share-form.html- Generated by GHA #6668

  • why: Requires review to determine action. See Resolve CodeQL Alert #49 in wins-share-form.html- Generated by GHA #6668 (comment) (ready for dev lead and added to the dev/pm agenda 2025-08-25 for adding to 2025-09-08
  • status: Ice Box
    • draft: False
    • responsible: None
  • role: front end

• ER: Feasibility of tracking the “Share your wins” and “Submit” buttons using Google Analytics #4388

  • why: so that post launch we know how people interacted with this page
  • status: Epics and ERs that are ready to be turned into issues
    • draft: False
    • responsible: None
  • role: backend/devOps

• UX research results re: Win social media strategy #3145

  • why: social media strategy for announcing launch
  • status: ice box
    • draft: True
    • responsible: None
  • role: product

Could Have

List of all could have issues

• 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
  • status: In Progress (actively working)
    • draft: False
    • responsible: daras-cu
  • role: Back end/devOps and front end

Details for Search icon-github.svg

Code files icon-github.svg appears in: GitHub Search icon-github.svg&type=code

Issue files icon-github.svg appears in: GitHub Search icon-github.svg&type=issues

• Resolve CodeQL Alert #34 - Generated by GHA #6672

  • why: Is dependent on a different issue being solved and is likely a false positive.
  • status: Ice box
    • draft: False
    • responsible: None
  • role: front end

• Modify wins.js to accept GitHub and LinkedIn usernames or complete URLs #5470

  • why: We need to modify wins.js so that if the existing GitHub/LinkedIn fields (which contain URLs) are not populated (see Add new fields to WINS Display Review and _wins-data.json #5472)
  • status: Ice box
    • draft: False
    • responsible: None
  • role: front end

• Set up notification email to submitter once their Win is published #3142

  • why: to create a better use experience that has them share it with other people
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: product

• Write copy explaining "brief overview" question on Wins form #3140

  • why: to get more people to complete their wins submissions (instead of dropping out)
  • status: prioritized backlog
    • draft: Draft
    • responsible: None
  • role: writing

• Google Apps Script: Migrate Wins Data - Delete AF file  #2148

  • why: Its technical debt and not crucial to the launch, but if we want to change anything about the wins card, or do dynamic card on the about page (which we removed from launch requirement), we will need this issue done.
  • status: Ice box
    • draft: False
    • responsible: None
  • role: back end/devOps

Won't have this time

List of all won't have issues

• Epic: Change to Wins Form, Apps Script and JS to implement new URL validation strategy #4671
• Fix the dropdown menu design for wins page #3627
• Design System Audit: Text Elements: Wins Page #3529
• Add editing feature for win submission form #3143

Template

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

List of all issue

• Review Needed - New Wins Form Submission #8427
• Review Needed - New Wins Form Submission #8426
• Review Needed - New Wins Form Submission #8280
• Review Needed - New Wins Form Submission #8279
• Review Needed - New Wins Form Submission #8145
• Update documentation for wins_data #7707
• EPIC: Prepare the Wins page and wins card randomizer for Homepage Launch #7664
• ER: Issues to examine new wins data will be posted to the old project board #7594
• Resolve CodeQL Alert #34 - Generated by GHA #6672
• Resolve CodeQL Alert #49 in wins-share-form.html- Generated by GHA #6668
• Modify wins.js to accept GitHub and LinkedIn usernames or complete URLs #5470
• Epic: Change to Wins Form, Apps Script and JS to implement new URL validation strategy #4671
• ER: Feasibility of tracking the “Share your wins” and “Submit” buttons using Google Analytics #4388
• Fix the dropdown menu design for wins page #3627
• Design System Audit: Text Elements: Wins Page #3529
• UX research results re: Win social media strategy #3145
• Add editing feature for win submission form #3143
• Set up notification email to submitter once their Win is published #3142
• Write copy explaining "brief overview" question on Wins form #3140
• Google Apps Script: Migrate Wins Data - Delete AF file  #2148

[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