Logo is invisible on GitHub's light theme
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 半天
- 新手友好度
- 25/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 领域
- design
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- TypeScript
- 星标
- 7
- 派生
- 2
- 平均合并
- 1 天 17 小时
- 30 天内合并 PR
- 17
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
NanoForge-dev/Engine 的其他 Issue
-
dependencies enhancement good first issue
难度 2/5 1-3 小时 新手友好度 78/100
NanoForge-dev/Engine#513 ·
维护者通常 1 天内回复
-
bug chore tests
难度 2/5 1-3 小时 新手友好度 77/100
NanoForge-dev/Engine#511 ·
维护者通常 1 天内回复
-
docs(network): TSDoc says ICE_SERVERS defaults to an empty list, the code uses public STUN servers未关闭documentation good first issue modules:network
难度 1/5 1 小时以内 新手友好度 88/100
NanoForge-dev/Engine#509 ·
维护者通常 1 天内回复
-
documentation modules:ecs packages:asset packages:core
难度 2/5 1-3 小时 新手友好度 82/100
NanoForge-dev/Engine#508 ·
维护者通常 1 天内回复
-
bug good first issue modules:music modules:sound
难度 2/5 1-3 小时 新手友好度 78/100
NanoForge-dev/Engine#505 ·
维护者通常 1 天内回复
查看 NanoForge-dev/Engine 的全部 Issue
相似的 Issue
-
Mend: dependency security vulnerability
难度 1/5 1-3 小时 新手友好度 65/100
fdm-monster/fdm-monster#5563 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
be-BOP-io-SA/be-BOP#2849 ·
-
难度 2/5 1-3 小时 新手友好度 79/100
维护者通常 1 天内回复
-
1️⃣ phase/under-investigation flaky/confirmed flaky/needs-decision type/bug
难度 2/5 1-3 小时 新手友好度 65/100
growilabs/growi#12246 · 3 条评论 ·
维护者通常 1 天内回复
-
🐛 The Rulekeeper - An index run that gives up on the lock ends Succeeded可能已有人在做 @github-actions 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
SSWConsulting/SSW.Rules#2809 · 1 条评论 ·
维护者通常 1 天内回复