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

未關閉
#77 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 3 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
18/100
Issue 類型
功能
描述清晰度
描述清楚
活躍度
冷清
技術堆疊
python

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.
主要語言
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 摘要。