Show the app in motion and say who it is for (demo GIF, accessibility and QA use cases)

未关闭
#117 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 3 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
55/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
冷清
技术栈
python
领域
documentation

调研方向

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 内容生成。

描述

documentation marketing priority: medium

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

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TMHSDigital/autoclicker 的其他 Issue

查看 TMHSDigital/autoclicker 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。