Pico-SDK use of Red Text on Pure Black Background Strains Eyes
@katshann-raspberry is already working on this.
Since Aug 10, 2026.
Assessment
This issue has not been assessed yet.
Description
The dark theme for the pico-sdk documentation is much appreciated, but it has some rough-edges.
In the pico-sdk, the web page uses a dark-red-text on black background that is very hard on the eyes. This isn't a major issue, but is something that would be very helpful to address and correct -- especially for older eyes.
I'm not a web designer, but have done a lot of dark-theme UI design. The choice of complementary colors that provide proper contrast for readability is crucial. There are a couple of axioms that the current colors used by the pico-sdk violate:
- never use dark text on dark backgrounds, (dark refers to the color-character, where, e.g. red is a "dark" color, while yellow is a "light" color);
- never use pure black for text or backgrounds (e.g.
#000000).
The current pico-sdk violates both. Here is a screenshot from the multicore - fifo documentation:
You can alter the red (or any "dark" color) by reducing the saturation to improve contrast (e.g. #FF6464), but with red that usually ends up looking a bit pinkish or orange, but is still much easier on the eyes than a dark red on black. Cyans work exceptionally well on a "close to black" background (something around #53C6FF) as do faux ambers (like #FFEAB0).
As far as replacing the pure black background with something close to pure black, a black desaturated cyan works really well to eliminate eye-strain. Anything in the range of #070A10 to #18191D works really well. You can even get by with a bit lighter and you can tweak the desaturated offset color to suit your taste. Text renders cleaner on something that isn't pure black and your eyes with thank you. (this github page uses #0D1117 which works fine)
Again, not a major issue, but something very easily corrected by changing a couple of color-codes. Then people would have no excuse for not RTFM...
If this isn't the proper place for this issue, just let me know and I'm happy to migrate it to wherever is proper. I looked at the raspberrypi/documentation repo, but that didn't seem like the right place for pico-sdk doc issues.
- Dominant language
- Python
- Stars
- 5.6k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No 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 raspberrypi/documentation
-
One Time Programmable memory map incorrectMay be free again @timg236 claimed this 85 days ago, and no pull request is open. Openwhite paper
raspberrypi/documentation#4319 · 2 comments · 2 assignees ·
-
GPIO and the 40-pin header: legend embedded in associated image is outdatedMay be free again @stevedavies-rp claimed this 100 days ago, and no pull request is open. Openbacklog diagram
raspberrypi/documentation#4124 · 3 comments · 1 assignee ·
-
Solution: Sync Flash to GS Camera with use of the XVS PIN and an Pico or ArduinoMay be free again @lucyhattersley claimed this 47 days ago, and no pull request is open. Openbacklog camera 📷 tutorial 📘
raspberrypi/documentation#4034 · 9 comments · 1 assignee ·
-
Update needed to "Raspberry Pi Debug Probe" for PICO 2May be free again @katshann-raspberry claimed this 100 days ago, and no pull request is open. Openbacklog restructure rp2040
raspberrypi/documentation#4003 · 10 comments · 1 assignee ·
-
How to change the primary UART of a Raspberry PiMay be free again @katshann-raspberry claimed this 99 days ago, and no pull request is open. Openbacklog documentation troubleshooting
raspberrypi/documentation#3938 · 1 comment · 1 assignee ·
All issues in raspberrypi/documentation
Similar issues
-
integration: media_player
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
home-assistant/core#193344 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
daniel-ospina/tortoise#13607 ·
Maintainers usually reply within 1 day
-
documentation priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day