Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

site: privacy-respecting usage analytics to learn what people search for and fail to find

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

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
45/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
javascript
領域
analytics

研究方向

Start by checking site/public/ and site/lib/ to confirm how the site is served and where search and filter behavior lives. Compare GoatCounter and Plausible against the stated privacy requirements, including Do Not Track, GPC, and the disabled bucket. Done means the dashboard reports page views, top searches, and zero-result searches, with collection details in the README and privacy information in the footer.

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

描述

enhancement priority: low

Why it matters
No analytics is a fine privacy default, but it means nobody can see which searches return zero results (a direct measure of coverage gaps), which filters are used, which entries are clicked and which stacks are read. Those numbers would steer what to add next better than research prompts.

Evidence

  • No analytics script in site/public/ or site/lib/.
  • The "request an asset" form is the only gap signal and depends on people filing.

Suggested approach
A cookie-less counter (GoatCounter or Plausible), one custom event for a zero-result search (query truncated, no identifiers) and one for a filter combination, a privacy line in the footer and README, honour Do Not Track / GPC, off on localhost.

Done when
A dashboard shows page views, top searches and zero-result searches, and the README states what is collected.

主要語言
JavaScript
星號
58
分支
15
平均合併
16 小時 53 分鐘
30 天內合併 PR
14

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

TMHSDigital/Free-Game-Dev-Assets 的其他 Issue

查看 TMHSDigital/Free-Game-Dev-Assets 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。