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

community: publish a "For publishers" page (what is recorded about you, how to correct it, preview opt-out, how to link back)

Closed Beginner friendly
  • Is something wrong?
#150 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
documentation

Research direction

Read the publisher-facing rules in CONTRIBUTING.md:84-92, the Correction form at correction.yml:21-26, the entry credit line in entry-page.mjs:106, and the README Contributing section. Add docs/for-publishers.md and the requested links and form option. Done means publishers can read the policy, correct a fact, and opt out of a preview without reading CONTRIBUTING.

Written by the indexing model from the issue text.

Description

community marketing priority: medium

Why it matters

Roughly 170 entries carry a publisher (Kenney, Quaternius, KayKit, Epic, Blender Studio, NASA and others). Publishers are the catalog's most credible amplifiers and the people most likely to notice an error, yet the rules that concern them are scattered across contributor sub-sections. Distinct from #117 (badge assets) and #112 (credit lines): this is the page those would link to.

Evidence (at 69387df)

  • Publisher-facing rules live only inside contributor docs: self-listing policy CONTRIBUTING.md:84-86; preview opt-out and pinning CONTRIBUTING.md:92. Removing a thumbnail is "open an issue" with no template option (the Correction dropdown at correction.yml:21-26 has no "I am the publisher / remove my preview" choice).
  • No page tells a publisher how the catalog describes their licence, that the quote is theirs and dated, how they would be told of a change, or that entries never rehost (README.md:22-24 is phrased for consumers).
  • The entry-page caption "Preview image from Kenney, shown under CC0" (entry-page.mjs:106) is already a visible publisher touchpoint with no destination to read more.

Suggested approach

docs/for-publishers.md (one screen): what an entry records, how to correct it (link the Correction form), how to be told about a re-read (subscribe to reverified.xml), preview policy and opt-out, self-listing rules, and "link to your entry" with the canonical URL pattern. Add "I am the publisher of this source" to the Correction form's dropdown. Link the page from the entry-page credit line and from the README Contributing section.

Done when

A publisher who finds their entry can read the policy, fix a fact and opt out of a preview without reading CONTRIBUTING.

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.