Update design for Status Page
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, scss
Research direction
Start by reading the customisations documented in nodejs/build pull request 2299 and review the current status page theme and its SCSS, HTML, and JavaScript constraints. Determine whether the work belongs in that pull request or this repository. Done means the status page design matches the site theme where possible and the resulting customisations are documented.
Written by the indexing model from the issue text.
Description
Enter your suggestions in details:
👋 Given the incident today, it seems folks have remembered that we have a status page (though it is very rarely used luckily). It'd be good to get the design updated on it to match the theme used on the site where possible.
Status page gives us very limited control, allowing for custom SCSS to be defined that'll apply globally to all pages and the ability to inject custom HTML (and JavaScript) in the footer of all pages.
The current customisations are documented in https://github.com/nodejs/build/pull/2299. Either we get that PR updated to capture new changes, or perhaps documenting those would be better in this repository now.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 6.5k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 29
Contributor 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 nodejs/nodejs.org
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nodejs/nodejs.org#9162 · 1 comment ·
-
web-agenda
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nodejs/nodejs.org#9098 · 3 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
nodejs/nodejs.org#8828 · 4 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
nodejs/nodejs.org#9166 · 3 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
nodejs/nodejs.org#9140 · 10 comments · 3 reactions ·
All issues in nodejs/nodejs.org
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100