建议：补齐讨论区、短视频与站点入口 / Proposal: discussions, short videos and a landing page

[LUgABeEEE]

这是一份社区/宣传向的提案，不涉及代码改动。若方向有偏差，欢迎直接在下面纠偏。
A community and outreach proposal — no code change implied. Corrections are welcome in the replies.

中文

现状

• 项目已有很扎实的基础：中英双语文档、几十个真实 issue 的反馈、0.6.x 的连续发布、跨版本 CI 矩阵。缺的不是内容，是入口。
• 新用户的第一站是 README；README 擅长讲清原理，不擅长回答「我这种情况怎么办」。
• 同类问题在 issue 里反复出现（连接、证书、模块加载），却没有低门槛的问答区。
• 演示材料散落在文档与截图里，没有一段「从零到手机可用」的视频。
• 没有页面能让人在 30 秒内判断「这是什么、我能不能用、怎么装」。

三项建议（按性价比排序）

1. 用起 GitHub Discussions（成本最低，收益最快）

• 分类已现成（Announcements / General / Q&A / Ideas / Polls / Show and tell）。建议把「提问」引导到 Q&A，issue 只留可复现的 bug 与已确认的改进；否则 issue 列表会继续被「我连不上」淹没。
• 不把新的聊天群（微信/QQ/Discord）作为第一入口：消息不可搜索、无法沉淀、答案要重复。若确需群，定位成补充，并约定「结论回帖到 Discussions」。
• 成本：两条置顶帖（怎么提问、常见故障索引）；之后每周约 15 分钟把重复问答合并进 FAQ。

2. 一套 3–5 分钟的视频（录一次，长期复用）

• 先做三段，每段 ≤3 分钟：① 从零到能用（安装 → 开局域网 → 扫码配对 → 手机上打开）；② 慢链路/连不上的排查（health、局域网 vs 远程、证书与配对状态）；③ 模块与体积（首屏为什么大、怎么排除可选模块，依赖规则要讲清）。
• 同一素材配中英字幕，B站 + YouTube，README 顶部放缩略图链接。
• 关键：命令与界面必须对齐当前版本；录制脚本和版本号留在仓库里，避免下次发版即过期。

3. 单页站点（承接搜索与分享）

• 结构：一句话定位 → 30 秒演示 → 三步安装 → 功能截图（复用 docs/screenshots）→ FAQ → 下载/仓库/Discussions 入口。
• GitHub Pages 部署，内容源仍是 docs/；站点只做聚合，避免两份文档各写各的。
• 不做「又一个完整文档站」：文档留在仓库，页面只负责让人决定要不要用。

建议顺序

1. 本周：两条置顶帖 + 把「提问」模板指向 Q&A（约半天）；
2. 下个版本窗口：录第一段视频（半天到一天）；
3. 视频上线后：单页站点（约一天），串起安装、排障、讨论三个入口。

能帮的部分

• Q&A 置顶帖与提问模板文案（中英）；
• 视频分镜与录制脚本（命令、界面步骤、需避免的隐私信息）；
• 站点单页实现与 GitHub Pages 部署；
• 把现有 issue/PR 中反复出现的问答整理成 FAQ 初始条目。

不建议做的

• 同时开三个聊天群 + Discussions：分流比没有入口更糟；
• 把文档搬进站点再维护一份：两份必然不同步；
• 用宣传掩盖未解决的安装问题：先把安装与排障讲透。

English

Where the project stands

• The foundations are solid: bilingual docs, dozens of real-world issues, a steady 0.6.x release cadence, and a cross-version CI matrix. What is missing is not content — it is an entrance.
• The README is the first stop for new users, but it explains the design better than it answers "what about my situation?".
• The same questions repeat in issues (connection, certificates, module loading) with no low-friction place to ask them.
• Demo material is scattered across docs and screenshots; there is no short "zero to a working phone" video.
• There is no page that lets someone decide in 30 seconds whether this is for them, and how to install it.

Three proposals (ordered by value for effort)

1. Use GitHub Discussions (cheapest, fastest payoff)

• The categories already exist (Announcements / General / Q&A / Ideas / Polls / Show and tell). Route questions into Q&A and keep issues for reproducible bugs and confirmed improvements; otherwise the issue list keeps drowning in "it won't connect".
• Do not make a new chat group (WeChat/QQ/Discord) the primary entrance: messages are not searchable, not durable, and answers get repeated. If a group is still wanted, position it as a supplement and agree that conclusions get posted back to Discussions.
• Cost: two pinned posts (how to ask, troubleshooting index); then ~15 minutes a week folding repeated answers into the FAQ.

2. A set of 3–5 minute videos (record once, reuse for long)

• Start with three clips, each ≤3 minutes: (1) from zero to working — install, enable LAN access, pair via QR, open on the phone; (2) slow links and "it won't connect" — health checks, LAN vs remote, certificate and pairing state; (3) modules and payload size — why the first load is large, how to exclude optional modules, and the dependency rule.
• Same footage with bilingual subtitles on Bilibili and YouTube; link a thumbnail from the top of the README.
• The important part: commands and UI must match the current release; keep the recording script and its version in the repository so the next release does not silently invalidate it.

3. A single landing page (to capture search and sharing)

• Structure: one-line positioning → 30-second demo → three-step install → feature screenshots (reuse docs/screenshots) → FAQ → links to download, repository and Discussions.
• Deploy with GitHub Pages and keep docs/ as the source of truth; the site aggregates, it does not fork the documentation.
• Not "another full documentation site": documentation stays in the repository; the page exists so a reader can decide whether to use it.

Suggested order

1. This week: the two pinned posts, and point the "question" template at Q&A (~half a day);
2. Next release window: record the first video (~half a day to one day);
3. After the video exists: the landing page (~one day), connecting install, troubleshooting and Discussions.

What we can contribute

• Q&A pinned-post and question-template copy (Chinese and English);
• Video storyboard and recording script (commands, UI steps, what must be kept out of frame for privacy);
• Implementing the landing page and the GitHub Pages deployment;
• Turning recurring questions in existing issues/PRs into a starter FAQ.

What we would avoid

• Opening three chat groups plus Discussions: splitting attention is worse than having no entrance;
• Copying the docs into the site and maintaining both: they will diverge;
• Using promotion to paper over unresolved installation problems: make installation and troubleshooting solid first.

[LUgABeEEE]

这条建议已并入 #279 的移动适配线提案：讨论区、短视频、站点入口这组诉求已在那条提案的「同方向另两条」里列出，维护者的回复请统一到 #279，避免三条各聊各的。

This suggestion is folded into #279 together with #278, so the maintainer's reply can live in one place instead of three threads.

[saya-ch]

感谢提案，Discussions 分类与置顶 FAQ 的方向认可。另外：我个人精力有限，社群、网站、视频这些运营，你有兴趣接手的话，权限方面我可以给足，我们可以聊聊。

[LUgABeEEE]

我这边有一个两人的团队，正在做手机端优化，主要包括网关和UI优化两个部分。如果可以，我们可以先加一个联系方式，进行进一步的沟通。我对这个项目是非常认可，且非常有信心把他做好。也感谢你的认可。
另外，关于之前一批pr有些频繁以及未充分验证的问题，深感抱歉，新的pr会考虑这些问题，尽量合并一块提交

[LUgABeEEE]

我给你发了一份邮件，有我的联系方式。发到了你Github主页的那个邮箱了