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 摘要。