EPIC: Prepare the Projects page for Homepage Launch

[priyanka02art]

Overview

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

Relevance of the issues to the Homepage launch

Must Have

• EPIC: Prepare the Projects page for Homepage Launch #7666

  • why: It is the epic for this page (this issue)
  • status: In Progress (actively working)
    • draft: True
    • responsible: priyanka02art and nadiaspn0503
  • role: Product

• Correct Oxford Comma in Projects Page #8510

  • 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 Project Page.
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: Back end/devOps and front end

• Correctly Classify Tools and Technologies Used In Projects #8507

  • why: We need to correctly classify tools and technologies used in projects so users/volunteers have clarity on what systems are being used.
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: Front end

• Confirm Docker Usage and Classify Dockerfile Categorization #8506

  • why: We need to confirm Docker usage and ensure projects with Dockerfiles have Docker listed in their Technologies section, so users/volunteers have clarity on what systems are being used.
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: Project

• Fix Whiteboard / Paper & Pencil Tool Filter Bug #8496

  • why: We need to fix the bug on the projects and projects check pages that prevents the "whiteboard / paper & pencil" tool filter from being selected so that the website will work correctly.
  • status: New Issue Approval
    • draft: True
    • responsible: madcharlie02
  • role: Back end/devOps and front end

• ER: Address the difference between Docker and Dockerfile #8485

  • why: We need to Identify the difference between the Docker technology and Dockerfile language filters.
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: Front end

• Search/Filter Integration: Update Counter and Improve Visual Feedback #8467

  • why: We need to integrate the search bar with the filter system so that search terms update the filter counter, provide immediate visual feedback, and allow users to continuously add multiple search terms.
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

• Mobile View: Page Reset and Filter Bar Closing After Search #8466

  • why: We need to fix the mobile view search behavior so that the page maintains its scroll position and the filter bar remains open after a user performs a search.
  • status: New Issue Approval
    • draft: False
    • responsible: None
  • role: Front end

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

  • why: Need to have Projects 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 Projects page with correct information.
  • status: Ready for Prioritization
    • 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 Projects page with correct information.
  • status: Ready for Prioritization
    • draft: False
    • responsible: None
  • role: back end/devOps and front end

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

  • why: Helps PMs and leads know what to do with "Update Project Profile" ERs or epics with sub-issue(s) that have already been written
  • status: New Issue Approval
    • draft: True
    • responsible: JessicaLucindaCheng
  • role: dev leads, merge team, and product

• Epic: Make sure that the data in the project's page filters content is properly categorized #4434

  • why: We need to make sure that languages are not being added to tools and technologies fields on project.md cards and that items that should be in tools are not in technologies and vice versa
  • status: Ice Box
    • draft: False
    • responsible: None
  • role: Dev leads and Product

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

  • why: Ensure users receive accurate and relevant information to navigate seamlessly between projects.
  • status: In progress (actively working)
    • draft: False
    • responsible: kirandhamotharan
  • role: Product

Should Have

• ER: Improve the Chevron #8486

  • why: We need to improve the chevron to make it look better. The current one is unattractive.
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: Design and front end

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

  • why: without this projects that have more than one repo, will only have their primary repo show up on the project's page and their project info page
  • status: In Progress (actively working)
    • draft: False
    • responsible: JessicaLucindaCheng
  • role: Back end/DevOps and front end

Could Have

List of all could have issues

• Reorder the Unfiltered Display of all Projects #8490

  • why: Potentially we could remove the completed projects to an archived section unless we want to keep them on the site for visibility.
  • status: New Issue Approval
    • draft: True
    • responsible: None
  • role: back end/devOps and front end

• Update Project Filters: Remove OR Logic Across and Within Filter Categories #8353

  • why: Need to update 'Languages/Technologies/Tools' filter to be easier to navigate
  • status: In progress (actively working)
    • draft: False
    • responsible: aadilahmed
  • role: back end/devOps and front end

• Resolve CodeQL Alert #30 - Generated by GHA #6675 - this issue might get resolved before we launch but it's not required.

  • why: There seems to be an incorrect alert but not sure what action triggers the alert. need more clarity ExperimentsInHonesty
  • status: Ice Box
    • draft: False
    • responsible: None
  • role: Front End

• Create "List" view on Project and Toolkit pages #6143

  • why: To enhance user experience, add a "List View" button on the Projects and Toolkit pages for a more concise presentation of information.
  • status: Ice Box
    • draft: True
    • responsible: None
  • role: Front End

Won't have this time

List of all won't have issues

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

Templates

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

### Issues list associated with this epic
last updated: YYYY-MM-DD
Highest number found:

List of all issue by number

• Correct Oxford Comma in Projects Page #8510
• Correctly Classify Tools and Technologies Used In Projects #8507
• Confirm Docker Usage and Classify Dockerfile Categorization #8506
• Fix Whiteboard / Paper & Pencil Tool Filter Bug #8496
• Reorder the Unfiltered Display of all Projects #8490
• ER: Improve the Chevron #8486
• ER: Address the difference between Docker and Dockerfile #8485
• Search/Filter Integration: Update Counter and Improve Visual Feedback #8467
• Mobile View: Page Reset and Filter Bar Closing After Search #8466
• Update Project Filters: Remove OR Logic Across and Within Filter Categories #8353
• 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
• Instructions for What to Do With "Update Project Profile" ERs #8054
• EPIC: Prepare the Projects page for Homepage Launch #7666
• ER: Rationalizing the sponsors and partners info in code base #6819
• Resolve CodeQL Alert #30 - Generated by GHA #6675
• Create "List" view on Project and Toolkit pages #6143
• Rollout Plan: Change code to read data from multiple project repositories #6138
• Epic: Make sure that the data in the project's page filters content is properly categorized #4434
• Review project data to determine reclassifying requirements for their Technologies and Tools. #4262

[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