Show the app in motion and say who it is for (demo GIF, accessibility and QA use cases)
维护者通常 3 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 55/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 冷清
- 技术栈
- python
调研方向
Start with README.md and docs/index.html, which the issue identifies as the places with the existing screenshot and landing page. Check the project’s release notes or template for where release content is assembled. Done means the demo appears in the README, landing page, and next release, and a "Who it's for" section appears in both docs.
由索引模型根据 Issue 内容生成。
描述
Why it matters
A static screenshot of Fixed mode undersells recording and image targets, which are only convincing when you see them. And the project never says who it is for. People with RSI or limited motor control search for "auto clicker for RSI" and are well served by hold mode and key repeat; testers and data-entry users are another audience. Naming them is a credible, non-gaming framing that fits the "use responsibly" stance.
Evidence
- README (~lines 30-34) and the landing hero have one static screenshot.
grep -i "accessib\|motor\|RSI"in README.md and docs/index.html finds nothing.- The v1.6.0 release body is the raw changelog with no headline summary.
Suggested approach
- 10 to 15 s GIF/WebM (under 2 MB): Record, Play, corner failsafe stop. Plus stills of the Sequence and Image panels.
- A short "Who it's for" section in README and landing page: accessibility, software testing/QA, repetitive data entry, idle games where allowed. No claims beyond what exists.
- Release notes template: 2 to 3 headline bullets, the GIF and install commands above the changelog.
Done when
The demo appears in README, landing page and the next release; "Who it's for" ships in both docs.
- 主要语言
- Python
- 星标
- 0
- 派生
- 2
- 平均合并
- 2 天 13 小时
- 30 天内合并 PR
- 2
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
TMHSDigital/autoclicker 的其他 Issue
-
maintenance priority: low
难度 3/5 半天 新手友好度 56/100
TMHSDigital/autoclicker#202 ·
维护者通常 3 天内回复
-
bug priority: low
难度 3/5 1-2 天 新手友好度 52/100
TMHSDigital/autoclicker#201 ·
维护者通常 3 天内回复
-
dependencies maintenance priority: medium
难度 5/5 一周以上 新手友好度 35/100
TMHSDigital/autoclicker#154 · 1 条评论 ·
维护者通常 3 天内回复
-
marketing packaging priority: low
难度 4/5 3-5 天 新手友好度 38/100
TMHSDigital/autoclicker#118 · 1 条评论 ·
维护者通常 3 天内回复
-
ci packaging priority: medium
难度 4/5 3-5 天 新手友好度 47/100
TMHSDigital/autoclicker#91 · 1 条评论 ·
维护者通常 3 天内回复
查看 TMHSDigital/autoclicker 的全部 Issue
相似的 Issue
-
hive size:simple
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)未关闭
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 70/100
painted-porch/marcus#977 ·
维护者通常 1 天内回复
-
llm translation
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
FAIRmat-NFDI/sand#239 ·
维护者通常 1 天内回复