Skip to content

ER: Changing the "Rebooting" project status color #8860

Open

Description

@daras-cu

Emergent Requirement - Problem

We need to change the color of the "Rebooting" project status label to differentiate it from the "Completed" status.

Issue you discovered this emergent requirement in

Date discovered

Oct 26, 2026

Did you have to do something temporarily

  • YES
  • NO

Who was involved

@yielderdev
@daras-cu
@ExperimentsInHonesty

What happens if this is not addressed

Both "Rebooting" and "Completed" projects will have similar light blue labels on their project cards, making them harder to differentiate.

Resources

  • Project statuses appear on the following pages: Homepage, Projects Page, and individual project pages, e.g. 311 Data
  • File where all color variables are defined: _sass/variables/_colors.scss
  • Files where color is assigned for the Rebooting status class: Files
  • Example of project cards on the homepage/projects page with "Completed" status in blue:
Image

Recommended Action Items

  • Make a new issue
  • Discuss with team
  • Let a Team Lead know

Potential solutions [draft]

  • In _sass/variables/_colors.scss add the color #E5D4FF as color-lavender under the Violets heading. Result:
// Violets
$color-blueviolet: #571DD1;
$color-redpurple: #8e1737;
$color-darkorchid: #981DD1;
$color-lavender: #E5D4FF;
  • In each of the files containing styles for the 'status-Rebooting' class, change the background-color to the new $color-lavender.

To test:

  • Create a second test branch and manually change one of the projects' status to "Rebooting" in the MD file (e.g. for 311 Data: _projects/311-data.md). Run the site in Docker to confirm that the Rebooting label shows with the correct color on the homepage, projects page, and the individual project page.
  • Push the test branch to your fork of the website repo on GitHub. Make sure you open the PR from your original working branch without the test changes, but include a link to the test branch and testing instructions for reviewers in the PR text.

Activity

  1. added
    role: front endTasks for front end developers
    Feature: Refactor CSSPage is working fine - CSS needs changes to become consistent with other pages
    size: 0.25ptCan be done in 0.5 to 1.5 hours
    EREmergent Request
    on Nov 1, 2026
  2. github-actions commented on Nov 1, 2026

    @github-actions
  3. added
    Complexity: SmallTake this type of issues after the successful merge of your second good first issue
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    and removed on Nov 1, 2026
  4. added this to the 05. Know HFLA milestone on Nov 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Complexity: SmallTake this type of issues after the successful merge of your second good first issueEREmergent RequestFeature: Refactor CSSPage is working fine - CSS needs changes to become consistent with other pagesIssue Making: Level 2Make issue(s) from an ER or EpicP-Feature: Projects pagehttps://www.hackforla.org/projects/ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritizationrole: front endTasks for front end developerssize: 0.25ptCan be done in 0.5 to 1.5 hours

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions