Pico-SDK use of Red Text on Pure Black Background Strains Eyes
@katshann-raspberry ci sta già lavorando.
Dal 10/8/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
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.
- Lingua principale
- Python
- Stelle
- 5.6k
- Fork
- 2.1k
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di raspberrypi/documentation
-
One Time Programmable memory map incorrectForse di nuovo libera @timg236 l’ha presa 85 giorni fa e non c’è nessuna pull request aperta. Apertawhite paper
raspberrypi/documentation#4319 · 2 commenti · 2 assegnatari ·
-
GPIO and the 40-pin header: legend embedded in associated image is outdatedForse di nuovo libera @stevedavies-rp l’ha presa 100 giorni fa e non c’è nessuna pull request aperta. Apertabacklog diagram
raspberrypi/documentation#4124 · 3 commenti · 1 assegnatario ·
-
Solution: Sync Flash to GS Camera with use of the XVS PIN and an Pico or ArduinoForse di nuovo libera @lucyhattersley l’ha presa 47 giorni fa e non c’è nessuna pull request aperta. Apertabacklog camera 📷 tutorial 📘
raspberrypi/documentation#4034 · 9 commenti · 1 assegnatario ·
-
Update needed to "Raspberry Pi Debug Probe" for PICO 2Forse di nuovo libera @katshann-raspberry l’ha presa 100 giorni fa e non c’è nessuna pull request aperta. Apertabacklog restructure rp2040
raspberrypi/documentation#4003 · 10 commenti · 1 assegnatario ·
-
How to change the primary UART of a Raspberry PiForse di nuovo libera @katshann-raspberry l’ha presa 99 giorni fa e non c’è nessuna pull request aperta. Apertabacklog documentation troubleshooting
raspberrypi/documentation#3938 · 1 commento · 1 assegnatario ·
Tutte le issue di raspberrypi/documentation
Issue simili
-
HassSetVolumeRelative reports no targets (empty success list) although the volume was changedApertaintegration: media_player
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
home-assistant/core#193344 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 82/100
daniel-ospina/tortoise#13607 ·
I maintainer di solito rispondono entro 1 giorno
-
documentation priority: medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
I maintainer di solito rispondono entro 1 giorno
-
needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno