Skip to content

Projects Pages: Update Project Status Options and Label Color #8776

Closed

Description

@kimberlyvaldez07

Prerequisites

  1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page and attend an onboarding session.
  2. You have already read our How to Contribute to Hack for LA Guide.

Overview

We need to add a new project status option for "Closed" projects and a new status label color scheme to ensure accuracy and distinction between the projects lifecycle.

Details

We are adding a "Closed" project status to accurately reflect retired projects that did NOT make it to completion. This is different from the "Completed" project status. Additionally, we are updating the color scheme by adding a color for the "Closed" status and changing the "Completed" status from red to blue.

Ignoring the shape of the labels, this is an example of what the colors should look like:

Image

Action Items

  • Review the Details section above

  • Add the new "Closed" project status label by updating statusList in assets/js/current-projects.js1 from:

    const statusList = ["Active","On Hold","Completed"]
    

    to:

    const statusList = ["Active","On Hold","Completed","Closed"]
    
  • Update the status label color variables for the "Closed" and "Completed" labels

    • Navigate to _sass/variables/_colors.scss 2

    • For the "Closed" status label, underneath the // Blacks, Greys, White section add the variable $color-mediumlightgrey: #D9D9D9:

      Update the following section from:

      // Blacks, Greys, White
      ...
      $color-mediumgrey: #cccccc;
      $color-lightgrey: #ededed;
      

      to:

      // Blacks, Greys, White
      ...
      $color-mediumgrey: #cccccc;
      $color-mediumlightgrey: #D9D9D9;
      $color-lightgrey: #ededed;
      
    • For the "Completed" status label, underneath the // Blues section add the variable, $color-paleblue: #B8D9FF:

      Update the following section from:

      // Blues
      $color-midnightblue: #173567;
      $color-darkroyalblue: #01548a;
      $color-blue: #046afa;
      ...
      

      to:

      // Blues
      $color-midnightblue: #173567;
      $color-darkroyalblue: #01548a;
      $color-blue: #046afa;
      $color-paleblue: #B8D9FF;
      ...
      
  • Implement the updated variables by navigating to the three following files:

    • _sass/components/_projects.scss3

    • _sass/components/_projects-page.scss4

    • _sass/components/_home.scss5

    • Update the "Completed" status class and create the "Closed" status class for each of the above files from:

      .status-Completed {
        background-color: $color-salmon;
      }
      

      to:

       .status-Completed {
         background-color: $color-paleblue;
       }
      
       .status-Closed {
         background-color: $color-mediumlightgrey;
       }
      
  • Verify the changes by viewing the following in your local environment with Docker and include before and after screenshots with your pull request:

    • Visit the Hack for LA website project page on localhost 6
    • To view and test the "Closed" label, select a project that is currently displayed on the website. Temporarily change the status: line of that project's projectname.md file in the _projects folder to status: Closed in your local copy of the repo only.
    • Take before and after screenshots of that project's label on the Projects page, and include them in your PR.
    • Change the status: line back to its original value, then run git status and confirm that the project file is not listed in your changes, so the test edit isn't committed.

Instructions for Merge Team

Resources

Footnotes

  1. https://github.com/hackforla/website/blob/gh-pages/assets/js/current-projects.js ↩

  2. https://github.com/hackforla/website/blob/gh-pages/_sass/variables/_colors.scss ↩

  3. https://github.com/hackforla/website/blob/gh-pages/_sass/components/_projects.scss ↩

  4. https://github.com/hackforla/website/blob/gh-pages/_sass/components/_projects-page.scss ↩

  5. https://github.com/hackforla/website/blob/gh-pages/_sass/components/_home.scss ↩

  6. Projects page URL: https://www.hackforla.org/projects/ ↩

Activity

  1. github-actions commented on Sep 4, 2026

    @github-actions
  2. changed the title [-]Update Project Status Options and Label Color[/-] [+]Projects Pages: Update Project Status Options and Label Color[/+] on Sep 4, 2026
  3. 39 remaining items

  4. yielderdev commented on Oct 10, 2026

    @yielderdev
  5. added and removed
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    DraftIssue is still in the process of being created
    on Oct 10, 2026
  6. removed their assignment
    on Oct 10, 2026
  7. moved this from New Issue Approval to Ready for Prioritization in P: HfLA Website: Project Boardon Oct 10, 2026
  8. moved this from Ready for Prioritization to Prioritized backlog in P: HfLA Website: Project Boardon Oct 10, 2026
  9. self-assigned this
    on Oct 11, 2026
  10. HackforLABot commented on Oct 11, 2026

    @HackforLABot
  11. yepezjuan commented on Oct 11, 2026

    @yepezjuan
    Member

    Availability: M,,TH,F (4-6pm)
    ETA: Oct 17

  12. daras-cu commented on Oct 11, 2026

    @daras-cu
    Member

    @yepezjuan I moved this to the in progress column for you, don't forget whenever you assign yourself to an issue to move it over.

  13. moved this from In progress (actively working) to QA in P: HfLA Website: Project Boardon Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Complexity: MediumP-Feature: Project Info and PageA project's detail page (e.g. https://www.hackforla.org/projects/100-automations)P-Feature: Projects pagehttps://www.hackforla.org/projects/p-feature: Projects-checkWe use this page to check to make sure that teams are using the Technology section correctlyrole: back end/devOpsTasks for back-end developersrole: front endTasks for front end developerssize: 0.25ptCan be done in 0.5 to 1.5 hours

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions