Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
#120 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
analytics

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
JavaScript
Stars
58
Forks
15
Avg merge
16h 53m
Merged PRs (30d)
14

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from TMHSDigital/Free-Game-Dev-Assets

All issues in TMHSDigital/Free-Game-Dev-Assets

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.