Discoverability: social preview, landing page, comparison section and a launch post

Offen
#77 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 3 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
18/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Ruhig
Tech-Stack
python

Rechercherichtung

Start with the README and the repository’s GitHub Pages settings; the issue proposes a static page in docs/ or a gh-pages branch, plus README edits and repository settings changes. Create the landing page with a download link and FAQ, add the factual comparison section, and prepare the social preview and launch announcement. Done means the homepage, social preview, landing page, README comparison, and announcements in at least two places are in place.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

documentation marketing priority: medium

Why it matters

The README is now genuinely good, but almost nobody reaches it: the repo has 0 stars, no homepage URL, and no custom social preview, so links shared on Reddit, Discord or X render as a generic GitHub card. "Autoclicker" is a crowded search space dominated by long-standing closed-source tools, so this project needs a clear "why this one" message and a place search engines can index.

Evidence

  • gh repo view: homepageUrl empty; Discussions disabled.
  • No social preview image set (repository Settings, Social preview).
  • README has no comparison to the tools people already know, even though this project has real differentiators: open source and auditable, built in CI with checksums and provenance, safety stops on by default, no system-wide keyboard hook (RegisterHotKey), no ads or bundled installers.

Suggested approach

  1. Social preview: a 1280x640 image (logo, tagline, screenshot) uploaded in repo settings.
  2. Landing page on GitHub Pages (single static page in docs/ or a gh-pages branch): hero with download button, the safety story, timing diagram, FAQ ("Is it safe?", "Why does SmartScreen warn?", "Does it work in games?"). Set it as the repo homepage.
  3. "Why this one" section in README and page: a short, factual comparison table against typical freeware autoclickers (open source, verifiable builds, no installer, safety defaults, multi-monitor). Keep wording neutral and avoid "anti-detection" phrasing per project conventions.
  4. Launch: post a 1.5.0 announcement in relevant communities (r/software, r/windows, r/opensource), add to curated lists (e.g. awesome-windows), and enable Discussions for Q&A.

Done when

  • The repo has a homepage URL, a custom social preview, a landing page with download and FAQ, and a README comparison section; the 1.5.0 release has been announced in at least two places.
Vorherrschende Sprache
Python
Sterne
0
Forks
2
Ø Merge
2 T. 13 Std.
Gemergte PRs (30 T.)
2

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus TMHSDigital/autoclicker

Alle Issues in TMHSDigital/autoclicker

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.