Logo is invisible on GitHub's light theme
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- Medio día
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Error
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Área
- design
Línea de trabajo
The payload names no file, component or theme setting; it links only to the NanoForge-dev organisation and a screenshot of the logo in white mode. Start by finding the theme toggle and the logo asset the screenshot shows, then check how the logo is styled under the light theme. Done means the logo stays readable in white mode, which you can confirm by switching themes and comparing against the screenshot. Ask in the issue which logo file is meant before you change anything.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
What is the type of issue?
Something else
What is the issue?
The NanoForge logo does not show well on GitHub's light theme: it is drawn for a dark background, and there is only one version of it.
- The org profile (NanoForge-dev/.github
profile/README.md) embedsprofile/logo.pngwith a plain<img>. - Every Engine README embeds
.github/logo.pngthe same way, through ablob/URL, e.g. the root README and modules/ecs (16 READMEs in total). - No README in the org has a light/dark variant (no
<picture>orprefers-color-scheme). The other repos (CLI, Loader, Editor, actions, API, components-systems, examples, landing, the web apps) use the same single logo.
Screenshot of the org profile in light mode:
Expected:
- A light-theme and a dark-theme logo file.
- Each README shows the logo with
<picture>and<source media="(prefers-color-scheme: dark)">/(prefers-color-scheme: light), using raw image URLs (https://raw.githubusercontent.com/...), notblob/URLs. - Done in the org profile README and in every Engine README that embeds
logo.png.
#466 changes the same <img> lines (the blob/ URL does not render outside GitHub): fix both in one PR.
Open questions (not recorded, ask the team):
- The org profile lives in
NanoForge-dev/.github: transfer this issue there and keep #466 for the Engine READMEs, or keep it here? - Who provides the light-theme logo file?
- Fix the other repos' READMEs in the same pass (one issue per repo), or not?
Where did you find it?
https://github.com/NanoForge-dev (org profile, light theme), and every Engine README, e.g. https://github.com/NanoForge-dev/Engine/blob/35f5644b821d6dedf3cdb3c4d2d5d4ab84f54f21/README.md#L4
- Lenguaje dominante
- TypeScript
- Estrellas
- 7
- Forks
- 2
- Merge medio
- 1 d 17 h
- PR fusionados (30 d)
- 17
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de NanoForge-dev/Engine
-
dependencies enhancement good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
NanoForge-dev/Engine#513 ·
Los mantenedores suelen responder en 1 día
-
bug chore tests
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
NanoForge-dev/Engine#511 ·
Los mantenedores suelen responder en 1 día
-
docs(network): TSDoc says ICE_SERVERS defaults to an empty list, the code uses public STUN serversAbiertodocumentation good first issue modules:network
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
NanoForge-dev/Engine#509 ·
Los mantenedores suelen responder en 1 día
-
documentation modules:ecs packages:asset packages:core
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
NanoForge-dev/Engine#508 ·
Los mantenedores suelen responder en 1 día
-
bug good first issue modules:music modules:sound
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
NanoForge-dev/Engine#505 ·
Los mantenedores suelen responder en 1 día
Todos los issues de NanoForge-dev/Engine
Issues similares
-
Mend: dependency security vulnerability
Dificultad 1/5 1-3 horas Aptitud para principiantes 65/100
fdm-monster/fdm-monster#5563 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
be-BOP-io-SA/be-BOP#2849 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
Los mantenedores suelen responder en 1 día
-
1️⃣ phase/under-investigation flaky/confirmed flaky/needs-decision type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
growilabs/growi#12246 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
🐛 The Rulekeeper - An index run that gives up on the lock ends SucceededPosiblemente ocupada @github-actions la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
SSWConsulting/SSW.Rules#2809 · 1 comentario ·
Los mantenedores suelen responder en 1 día