Update the Chat page to highlight Discord info and de-emphasize/remove outdated links
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 72/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- markdown
调研方向
定位渲染 chat.html 的源文件,并检查 Community channels 部分。将 Discord 作为主要选项,并提供其规则和 FAQ 指引,同时明确标记 IRC、论坛和 wiki 为次要或过时的替代方案;验证渲染后的 Chat 页面及其链接。
由索引模型根据 Issue 内容生成。
描述
The gbdev.io home page has, at the very top:
Game Boy Development community
We are a non for profit collective of passionate developers and hackers working on development tools, homebrew games, emulators, preservation and documentation for the Nintendo Game Boy handheld console, the original gray brick from 1989.
This is great! All the social links are actively updated, and the Discord link is where the reader can truly join the community, and start chatting with us. (Maybe it should be listed first?)
However, the Chat page is not. Here's what it currently says:
Join our community on the following channels. Before posting, read the rules and the FAQ (usually in the welcome threads or in the signup).
- Discord Server.
- IRC:
#gbdevon Libera.chat is bridged to the Discord chat.
#gbdev-ot,#gbdev-casual,#gbdev-hw,#gbdev-meta,#gbdev-asm,#gbdev-gfx,#gbdev-emudev,#gbdev-romhackingand#gbdev-researchare also available for discussion about specific topics.- Forum: https://gbdev.gg8.se/forums/
- Wiki: https://gbdev.gg8.se/wiki/
The first link is fine, but I think the second link looks a lot more important than it is (to the point of de-emphasizing the first link where we actually want people to go), and the last two links are basically dead.
The GBDev Discord is the place where members new and old can actually communicate. I think the "Before posting, read the rules and the FAQ" instruction should be a sub-bullet of this link, so it can be more precise about where to find that info once you join the server.
The IRC server basically just exists in 2026 as a bridge to Discord, and even that only for perhaps a dozen[^1] people. (Only one of whom I'd recognize as actually regularly using it, beware.) We shouldn't encourage new users to do the same, since it can't handle replies, videos, reactions, etc. But having the longest list item makes it look more important than it is.
The forum looks dead. The last post in its "Site News" is from 2019. Only 2 of the 7 sub-forums have posts from 2026, and only the one from March has a reply (the one from February went unanswered). (It's now July.)
The wiki also looks dead. I mostly know it as being the old Pan Docs site -- the very first link in the very first section of its Main Page, "Developer Information -> Documentation", starts off with a big red "The copy of Pan Docs hosted on this wiki is considered deprecated" banner (as some may recognize from outdated links via Google et al). I thought maybe there'd be more than just the old Pan Docs, since supposedly "A few articles up -> There a couple of articles up on the Wiki." But as of today there were no changes to any page in the last 30 days. (It's not even really a "chat" method; still at least a collaborative community effort, but nobody new to the community should be futilely trying to share info by editing this website.)
I don't think these should all still be presented as four equal-weight options. Explaining how to join and use the Discord server should be the primary purpose of this page. Then maybe in a <hr>-separated bottom section, or some other clearly secondary area, it could list the IRC, wiki, and forums as historical alternatives, and mention that they're less likely to be read/responded to any more.
[^1]: Edit: Turns out that, not counting me, there's 13, a whole baker's dozen! None of whom are talking. :P Oh, and one is the gb-bridge bot, so I guess it's max 12 real humans after all. Even the #pret channel has 25 others, despite pret only mentioning it at pret.github.io, not in its repos' READMEs.
- 主要语言
- Assembly
- 星标
- 34
- 派生
- 16
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
gbdev/gbdev.github.io 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 72/100
gbdev/gbdev.github.io#86 ·
-
help wanted question
难度 5/5 一周以上 新手友好度 20/100
gbdev/gbdev.github.io#103 · 54 条评论 · 2 个 reaction ·
-
难度 2/5 1-3 小时 新手友好度 35/100
gbdev/gbdev.github.io#89 ·
-
难度 3/5 1-2 天 新手友好度 20/100
gbdev/gbdev.github.io#88 ·
-
难度 5/5 一周以上 新手友好度 15/100
gbdev/gbdev.github.io#81 · 1 条评论 ·
查看 gbdev/gbdev.github.io 的全部 Issue
相似的 Issue
-
copilot documentation
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 2 天内回复
-
external-issue to-triage
难度 1/5 1 小时以内 新手友好度 90/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 92/100
维护者通常 2 天内回复
-
skill:code-review
难度 1/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复