EPIC: Prepare the Project Pages page for Homepage Launch

[priyanka02art]

Overview

We need to track existing issues and make new issues to deliver Project Pages 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: Project Info and Page
  • 1.01.01 Issue Tab: P-Feature: Project Info and Page
  • 1.01.02 Project Board: P-Feature: Project Info and Page
• 1.02 URL of page on Hack for LA website: A project's detail page (e.g. https://www.hackforla.org/projects/100-automations)
• 1.03 URL of link to code search: repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// Project Info and Page
• 1.04 URL of WIKI page: https://github.com/search?q=repo%3Ahackforla%2Fwebsite+Project+Info+and+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

• Reorder the unfiltered display of all projects from Active to On Hold to Completed. Potentially we could remove the completed projects to an archived section unless we want to keep them on the site for visibility.

---

last updated: 2026-1-6
Highest number found: 8450

Relevance of the issues to the Homepage launch

Must Have

• EPIC: Prepare the Project Pages page for Homepage Launch #7679

  • why: This issue
  • status: In progress (actively working)
    • draft: False
    • responsible: nadiaspn0503
  • role: product

• Update Project Profile: Website- Remove Ren Demeis-Ortiz #8450

  • why: Need to have Project Pages page with correct information.
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Update Project Profile: Hackforla.org Website Add Kerstin Carson #8440

  • why: Need to have Project Pages page with correct information.
  • status: No status
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Review and align language across documentation and interface elements #8407

  • why: Need to ensure that text used across the project follows consistent tone, terminology, and style conventions
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: missing

• Update Project Profile: HackforLA Website Add Ryan Keller #8398

  • why: Need to have Project Pages page with correct information.
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Update Project Profile: HackforLA Website #8362

  • why: Need to have Project Pages page with correct information.
  • status: Questions / In Review
    • draft: False
    • responsible: @aymeviviana
  • role: back end/devOps and front end

• Update Project Profile: Hackforla.org Website Add Xavier Neal-Carson #8361

  • why: Need to have Project Pages page with correct information.
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Update Project Profile: Hackforla.org Website Add Darshin Van Parijs #8360

  • why: Need to have Project Pages page with correct information.
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Update Project Profile: TDM Calculator #8348

  • why: Need to put the most recent One Sheet on the website.
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Update Project Profile: Hackforla.org Website Add Phalguni Kambhalur #8347

  • why: Need to have Project Pages page with correct information.
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Update Project Profile: Hackforla.org Website Remove Samhitha Kamma #8346

  • why: Need to have Project Pages page with correct information.
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• ER: We Need To Change the Status of the BOP Project to On Hold #8344

  • why: Need to list only active projects
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: back end/devOps

• Update Project Profile: Website Remove Mugdh Chauhan #8337

  • why: Need to have Project Pages page with correct information.
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Update Project Profile: Civic Tech Jobs (Add Tech: MKDocs) #8334

  • why: Need to have Project Pages page with correct information.
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Update Project Profile: Civic Tech Jobs (Add Tech: AWS) #8333

  • why: Need to have Project Pages page with correct information.
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Update Project Profile: Civic Tech Jobs (Add Tech: Vite) #8332

  • why: Need to have Project Pages page with correct information.
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Update Project Profile: HackforLA Website Add Donovan Vernon #8329

  • why: Need to have Project Pages page with correct information.
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Update Project Profile: Expunge Assist Add Farnaz S #8318

  • why: Need to have Project Pages page with correct information.
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Update Project Profile: Civic Tech Jobs Remove Terence Lo #8287

  • why: Need to have Project Pages page with correct information.
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Update Project Profile: Civic Tech Jobs - Add Jason Shi #8111

  • why: Need to have Project Pages page with correct information.
  • status: Prioritized backlog
    • draft: False
    • responsible: None (Was assigned to MohamedTwahir who experienced a technical problem added ready for merge team label)
  • role: back end/devOps and front end

• Instructions for What to Do With "Update Project Profile" ERs #8054

  • why: Need to have Project Pages page with correct information.
  • status: New Issue Approval - LM 2025-09-17
    • draft: True
    • responsible: JessicaLucindaCheng
  • role: dev leads, merge team, and product

• ER: Update wiki pages for project page #6412

  • why: Need to have Project Pages page with correct information.
  • status: ERs and epics that are ready to be turned into issues
    • draft: False
    • responsible: None (Added to HfLA: Dev/PM Agenda and Notes - 2025 #7859 (comment))
  • role: back end/devOps

• Rollout Plan: Change code to read data from multiple project repositories #6138

  • why: To change the HfLA website code to read from as many repositories as specified per project
  • status: In progress (actively working)
    • draft: False
    • responsible: JessicaLucindaCheng
  • role: back end/devOps and front end

• Add additional repo(s) for project: Access the Data #5127

  • why: To update the languages for Access the Data so that visitors to the website can find accurate and up-to-date information.
  • status: Ice box
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Rollout Plan: Move, refactor, and add SDG info and images #4153

  • why: Move, refactor and add SDG info and images for the rollout plan.
  • status: In progress (actively working)
    • draft: False
    • responsible: JessicaLucindaCheng
  • role: Dev leads

Should Have

• ER: Review the project.yml file template and files to fix the section for SDG info #6277

  • why: To reduce duplicate data
  • status: In progress (actively working)
    • draft: False
    • responsible: JessicaLucindaCheng
  • role: back end/devOps

• Display all the contributions for each person in a project that has 2 or more repos #6144

  • why: Need to change the code for displaying contribution data for each person in a project that has 2 or more repositories (repos). This is used for the All-Time Contributors section of each project's detailed page.
  • status: New Issue Approval
    • draft: True
    • responsible: JessicaLucindaCheng
  • role: back end/devOps

• Wiki: Project Profile Issue Template #5630

  • why: Makes it easier to convert stakeholder requests into actionable developer issues.
  • status: New Issue Approval
    • draft: True
    • responsible: JessicaLucindaCheng
  • role: back end/devOps and front end

Could Have

List of all could have issues

• Epic: Create issues to populate github-handle variable in leadership teams #8428

  • why: Create issues to populate the github-handle variable with the correct handle for each member of the leadership team
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: back end/devOps and front end

• Update Github handle for Santiago Vidal: Website #8423

  • why: To display the correct GitHub profile link for the contributor
  • status: In progress (actively working)
    • draft: False
    • responsible: Colombianah
  • role: back end/devOps and front end

• Add github-handle for Michael Morgan in lucky-parking.md #7801

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Greg Pawin in lucky-parking.md #7799

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Mark Jackson in public-tree-map.md #7795

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Isabelle Wagenvoord in public-tree-map.md #7794

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Mya Stark in not-today.md #7781

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Jacob Zwang in new-schools-today.md #7765

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Joshua Bubar in new-schools-today.md #7764

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Ben Swerdlow in new-schools-today.md #7763

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Tugba Metinyurt in open-community-survey.md #7435

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Snow in open-community-survey.md #7434

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Ambareen Sultana in open-community-survey.md #7432

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Kalyani Raman in open-community-survey.md #7431

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Bonnie Wolfe in open-community-survey.md #7430

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Sarah Port in hellogov.md #7402

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Kate Rose in hellogov.md #7401

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Hunter Owens in work-for-la.md #7384

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Add github-handle for Bonnie Wolfe in guides-teams.md #7102

  • why: Create a single variable to hold a GitHub handle
  • status: Prioritized backlog
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• ER: Add start dates and end dates to projects #6820

  • why: Dates needed for the future but are not currently needed.
  • status: ERs and epics that are ready to be turned into issues
    • draft: False
    • responsible: None
  • role: back end/devOps

• ER: Rationalizing the sponsors and partners info in code base #6819

  • why: To reduce scattered information and solve an emerging problem
  • status: Ice box
    • draft: True
    • responsible: ExperimentsInHonesty
  • role: back end/devOps

• ER: Add a link and details about how to edit pages to the wiki #6321

  • why: To make it easy for future team members to edit.
  • status: Ice box
    • draft: False
    • responsible: None
  • role: front end

• Move the commit for Jupyter Notebook from Access the Data repo to Data Science CoP repo #6139

  • why: To update the languages for Access the Data for website users to find accurate and up-to-date information
  • status: In progress (actively working)
    • draft: False
    • responsible: JessicaLucindaCheng
  • role: back end/devOps and front end

• End to end testing of display of events using Selenium  #6017

  • why: Ensures meetings display correctly on Project pages
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: back end/devOps

• Epic: Create issues to add github-handle to leadership teams #5441

  • why: Create a single variable to hold a GitHub handle
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Roll Out: Refactor GitHub handle in project files #5440

  • why: Create a single variable to hold a GitHub handle
  • status: Ice box
    • draft: False
    • responsible: None
  • role: back end/devOps

• Review project data to determine reclassifying requirements for their Technologies and Tools. #4262

  • why: To identify and update the technologies and tools requirement for all the projects.
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: product

• Create issues for new project impact content to be added to project md files #2037

  • why: To add information to each project md file to be displayed on the new Impact format.
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: product

• Create project card for Slack Redactor  #312

  • why: Provide collateral for the HackforLA website
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: product

Won't have this time

List of all won't have issues

• Update Project Profile: BOP #7726
• ER: A project that Hack for LA completed in the past is missing from the website #4342
• Design System Audit: Text Elements: Individual Projects Page #3526

Templates

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

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

List of all issue by number

• Update Project Profile: Website- Remove Ren Demeis-Ortiz #8450
• Update Project Profile: Hackforla.org Website Add Kerstin Carson #8440
• Epic: Create issues to populate github-handle variable in leadership teams #8428
• Update Github handle for Santiago Vidal: Website #8423
• Review and align language across documentation and interface elements #8407
• Update Project Profile: HackforLA Website Add Ryan Keller #8398
• Update Project Profile: HackforLA Website #8362
• Update Project Profile: Hackforla.org Website Add Xavier Neal-Carson #8361
• Update Project Profile: Hackforla.org Website Add Darshin Van Parijs #8360
• Update Project Profile: TDM Calculator #8348
• Update Project Profile: Hackforla.org Website Add Phalguni Kambhalur #8347
• Update Project Profile: Hackforla.org Website Remove Samhitha Kamma #8346
• ER: We Need To Change the Status of the BOP Project to On Hold #8344
• Update Project Profile: Website Remove Mugdh Chauhan #8337
• Update Project Profile: Civic Tech Jobs (Add Tech: MKDocs) #8334
• Update Project Profile: Civic Tech Jobs (Add Tech: AWS) #8333
• Update Project Profile: Civic Tech Jobs (Add Tech: Vite) #8332
• Update Project Profile: HackforLA Website Add Donovan Vernon #8329
• Update Project Profile: Expunge Assist Add Farnaz S #8318
• Update Project Profile: Civic Tech Jobs Remove Terence Lo #8287
• Update Project Profile: Civic Tech Jobs - Add Jason Shi #8111
• Instructions for What to Do With "Update Project Profile" ERs #8054
• Add github-handle for Michael Morgan in lucky-parking.md #7801
• Add github-handle for Greg Pawin in lucky-parking.md #7799
• Add github-handle for Mark Jackson in public-tree-map.md #7795
• Add github-handle for Isabelle Wagenvoord in public-tree-map.md #7794
• Add github-handle for Mya Stark in not-today.md #7781
• Add github-handle for Jacob Zwang in new-schools-today.md #7765
• Add github-handle for Joshua Bubar in new-schools-today.md #7764
• Add github-handle for Ben Swerdlow in new-schools-today.md #7763
• Update Project Profile: BOP #7726
• EPIC: Prepare the Project Pages page for Homepage Launch #7679
• Add github-handle for Tugba Metinyurt in open-community-survey.md #7435
• Add github-handle for Snow in open-community-survey.md #7434
• Add github-handle for Ambareen Sultana in open-community-survey.md #7432
• Add github-handle for Kalyani Raman in open-community-survey.md #7431
• Add github-handle for Bonnie Wolfe in open-community-survey.md #7430
• Add github-handle for Sarah Port in hellogov.md #7402
• Add github-handle for Kate Rose in hellogov.md #7401
• Add github-handle for Hunter Owens in work-for-la.md #7384
• Add github-handle for Bonnie Wolfe in guides-teams.md #7102
• ER: Add start dates and end dates to projects #6820
• ER: Rationalizing the sponsors and partners info in code base #6819
• ER: Update wiki pages for project page #6412
• ER: Add a link and details about how to edit pages to the wiki #6321
• ER: Review the project.yml file template and files to fix the section for SDG info #6277
• Display all the contributions for each person in a project that has 2 or more repos #6144
• Move the commit for Jupyter Notebook from Access the Data repo to Data Science CoP repo #6139
• Rollout Plan: Change code to read data from multiple project repositories #6138
• End to end testing of display of events using Selenium  #6017
• Wiki: Project Profile Issue Template #5630
• Epic: Create issues to add github-handle to leadership teams #5441
• Roll Out: Refactor GitHub handle in project files #5440
• Add additional repo(s) for project: Access the Data #5127
• ER: A project that Hack for LA completed in the past is missing from the website #4342
• Review project data to determine reclassifying requirements for their Technologies and Tools. #4262
• Rollout Plan: Move, refactor, and add SDG info and images #4153
• Design System Audit: Text Elements: Individual Projects Page #3526
• Create issues for new project impact content to be added to project md files #2037
• Create project card for Slack Redactor  #312

[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]

• Access the Data
  • Add additional repo(s) for project: Access the Data #5127
  • Rollout Plan: Change code to read data from multiple project repositories #6138
  • Display all the contributions for each person in a project that has 2 or more repos #6144
  • Update Project Profile: Access the Data #5337
• Expunge Assist
  • ER: Update Project Profile: Expunge Assist #6834
  • Update Project Profile: Expunge Assist (Remove Curtis Barber, Add Maria Weissman) #6866
  • ER: Update Project Profile: Expunge Assist #6579
• New Project
  • ER: A project that Hack for LA completed in the past is missing from the website #4342
• All project pages
  • ER: discrepancies in meeting data sourced from API calls to VRMS vs. vrms-data.json #6838
  • Update Project Info Page to show Meeting Description #6930
  • ER: Issue with Public Facing Slack Channel Links for Non members #6129
  • Update Project Info Page to show Meeting Description #6930
  • Update Team Meeting data on the Events page to show meeting frequency #6920
  • Improve accessible naming for resource icons in project pages #6655