ER: Changing the "Rebooting" project status color
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
Research direction
Start in _sass/variables/_colors.scss and add the proposed lavender variable under the Violets heading. Then find the status-Rebooting style rules (the repo code search linked in the issue) and point their background-color at the new variable. Done when the Rebooting label shows the new color on the homepage, projects page and a project page, checked by running the site in Docker with a test project set to Rebooting.
Written by the indexing model from the issue text.
Description
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
- #8776
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:
Recommended Action Items
- Make a new issue
- Discuss with team
- Let a Team Lead know
Potential solutions [draft]
- In
_sass/variables/_colors.scssadd the color #E5D4FF ascolor-lavenderunder 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-colorto 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.
- Dominant language
- JavaScript
- Stars
- 365
- Forks
- 872
- Avg merge
- 8d 19h
- Merged PRs (30d)
- 2
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hackforla/website
-
Complexity: See issue making label epic good first issue Issue Making: Level 1 P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt time sensitive
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Complexity: Small ER Feature: Refactor GHA Issue Making: Level 2 ready for merge team role: back end/devOps size: 0.25pt
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
hackforla/website#8871 · 1 comment ·
Maintainers usually reply within 1 day
-
Complexity: Small ER Feature: Refactor GHA Issue Making: Level 2 ready for merge team role: back end/devOps size: 0.25pt
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hackforla/website#8870 · 1 comment ·
Maintainers usually reply within 1 day
-
Complexity: Small P-Feature: Project Info and Page ready for merge team role: back end/devOps role: front end size: 0.25pt time sensitive
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
good first issue P-Feature: Project Info and Page Ready for Prioritization role: back end/devOps role: front end size: 0.25pt
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in hackforla/website
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
discovery:other factory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
vercel/ai#25068 · 4 comments ·
Maintainers usually reply within 1 day
-
needs-triage typo
Difficulty 1/5 Under an hour Newbie friendliness 88/100
llm-d-incubation/llm-d-scaling-manager#122 ·
Maintainers usually reply within 1 day
-
create-strapi-app doesn't await writing license.txt, so a failed write skips its error handlingOpenflag: invalid template issue: bug severity: low source: cli status: pending reproduction version: 5
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
strapi/strapi#28637 · 1 comment ·
Maintainers usually reply within 2 days