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
• Identify items that need issues opened

Resources/Instructions

• Parent Epic: homepage launch #2481

Used for creating this issue

• 1.01 Label name: 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:

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

Must Have

• 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
    • responsible: RW
  • role: backend/devOps

Should Have

• UX research results re: Win social media strategy #3145
  • why: social media strategy for announcing launch
  • status: icebox
  • role: product
• 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
  • role: backend/devOps

Could Have

• 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
  • role: writer
• 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
  • role: product
• Add new fields to WINS Display Review and _wins-data.json #5472
  • why: The URLs that appear on the wins page should be consistent, for professionalism
  • status: new issue approval
    • draft
    • responsible: RW
  • role: backend/devOps
• Modify wins.js to accept GitHub and LinkedIn usernames or complete URLs #5470
  • see Add new fields to WINS Display Review and _wins-data.json #5472
  • status: icebox

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
• Add editing feature for win submission form #3143
• Design System Audit: Text Elements: Wins Page #3529
• Google Apps Script: Add unique IDs as object keys for each wins entry #2385
• Create wiki page "Hfla Google Apps Script Development/Review Process" #4134
• Google Apps Script: Migrate Wins Data - Stop generation of AF file #2147
• Update wins.js so the Wins page uses icon-github.svg #6911
• Replace Github with GitHub in assets/js/wins.js updateOverlay #7495

Template

   - why: 
   - status: 
      - draft
      - responsible: 
   - role: 

List of all issue

• Google Apps Script: Migrate Wins Data - Stop generation of AF file #2147
• Google Apps Script: Add unique IDs as object keys for each wins entry #2385
• Fix the dropdown menu design for wins page #3627
• Write copy explaining "brief overview" question on Wins form #3140
• Set up notification email to submitter once their Win is published #3142
• Add editing feature for win submission form #3143
• UX research results re: Win social media strategy #3145
• Design System Audit: Text Elements: Wins Page #3529
• Create wiki page "Hfla Google Apps Script Development/Review Process" #4134
• ER: Feasibility of tracking the “Share your wins” and “Submit” buttons using Google Analytics #4388
• Epic: Change to Wins Form, Apps Script and JS to implement new URL validation strategy #4671
• Modify wins.js to accept GitHub and LinkedIn usernames or complete URLs #5470
• Add new fields to WINS Display Review and _wins-data.json #5472
• Update wins.js so the Wins page uses icon-github.svg #6911
• Replace Github with GitHub in assets/js/wins.js updateOverlay #7495
• ER: Issues to examine new wins data will be posted to the old project board #7594

[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