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

Ouverte
#117 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
55/100
Type d'issue
Documentation
Clarté
Clairement spécifiée
Activité
Calme
Stack technique
python
Domaine
documentation

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Python
Étoiles
0
Forks
2
Merge moyen
2 j 13 h
PR mergées (30 j)
2

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de TMHSDigital/autoclicker

Toutes les issues de TMHSDigital/autoclicker

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.