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

Abierto
#117 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Tranquilo
Stack tecnológico
python

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
0
Forks
2
Merge medio
2 d 13 h
PR fusionados (30 d)
2

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TMHSDigital/autoclicker

Todos los issues de TMHSDigital/autoclicker

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.