community: publish a "For publishers" page (what is recorded about you, how to correct it, preview opt-out, how to link back)
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 新手友好度
- 78/100
- Issue 類型
- 文件
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- javascript
研究方向
閱讀 CONTRIBUTING.md:84-92 中面向發布者的規則、correction.yml:21-26 中的 Correction 表單、entry-page.mjs:106 中項目的署名行，以及 README 的 Contributing 區段。新增 docs/for-publishers.md、要求的連結和表單選項。完成標準是發布者無須閱讀 CONTRIBUTING，就能閱讀政策、修正一項事實並選擇不接收預覽。
由索引模型根據 Issue 內容生成。
描述
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 pinningCONTRIBUTING.md:92. Removing a thumbnail is "open an issue" with no template option (the Correction dropdown atcorrection.yml:21-26has 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-24is 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.
- 主要語言
- JavaScript
- 星號
- 58
- 分支
- 15
- 平均合併
- 16 小時 53 分鐘
- 30 天內合併 PR
- 14
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
TMHSDigital/Free-Game-Dev-Assets 的其他 Issue
-
community marketing priority: low
難度 2/5 1-3 小時 新手友好度 72/100
TMHSDigital/Free-Game-Dev-Assets#151 ·
維護者通常 1 天內回覆
-
documentation priority: medium
難度 2/5 1-3 小時 新手友好度 78/100
TMHSDigital/Free-Game-Dev-Assets#72 ·
維護者通常 1 天內回覆
-
enhancement
難度 1/5 1-3 小時 新手友好度 68/100
TMHSDigital/Free-Game-Dev-Assets#3 · 1 則留言 ·
維護者通常 1 天內回覆
-
marketing priority: low
難度 2/5 1-3 小時 新手友好度 55/100
TMHSDigital/Free-Game-Dev-Assets#152 ·
維護者通常 1 天內回覆
-
feature priority: medium
難度 5/5 一週以上 新手友好度 25/100
TMHSDigital/Free-Game-Dev-Assets#144 ·
維護者通常 1 天內回覆
查看 TMHSDigital/Free-Game-Dev-Assets 的全部 Issue
相似的 Issue
-
Website未關閉good first issue
難度 2/5 1-3 小時 新手友好度 91/100
TanbirRamim/open-source-radar#314 ·
維護者通常 1 天內回覆
-
prio: medium
難度 2/5 1-3 小時 新手友好度 63/100
twentyhq/twenty#28826 · 1 則留言 ·
維護者通常 1 天內回覆
-
status: needs triage
難度 1/5 1-3 小時 新手友好度 76/100
mastra-ai/mastra#28382 · 1 則留言 ·
維護者通常 1 天內回覆
-
documentation
難度 2/5 1-3 小時 新手友好度 78/100
SolidGeeks/strata#21 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
Yomguithereal/mnemonist#247 ·