marketing: per-entry embeddable badge ("Licence read YYYY-MM-DD") and per-entry social cards
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- javascript
- 領域
- web-dev
研究方向
Start by reading site/lib/entry-page.mjs around lines 92–98 and site/build.mjs around lines 270–277, then inspect how entry IDs, licence families, and verified dates are represented. The issue proposes per-entry SVG badges, copyable Markdown and HTML snippets, unique PNG cards using the existing writer, and an outreach note in docs/. Done means every entry page has its own OG image and badge snippet; publisher adoption is also listed as a completion condition.
由索引模型根據 Issue 內容生成。
描述
Why it matters
Listed publishers (Kenney, Quaternius, KayKit, small itch creators) have a reason to link back if they get something: a badge saying their licence was independently read and dated. Each backlink is discoverability for the catalog and a trust signal for them. Separately, all 414 entry pages share one og-card.png, so a shared link to a specific entry looks identical to the home page on Discord, X and Slack.
Evidence
site/lib/entry-page.mjs:92-98uses the site-wide card for every entry.site/build.mjs:270-277renders the singleog-card.pngwith a dependency-free PNG writer.
Suggested approach
- Badge: a static SVG per entry at
dist/badge/<id>.svg("Free Game Dev Assets · CC0 · read 2026-10-13", coloured by licence family) plus a "Link to this entry" box with copyable Markdown and HTML. - Cards: generate
dist/entry/<id>/card.pngat build (name, licence, commercial badge, verified date) with the existing writer and pointog:imageat it. - A short "You're listed" note template in
docs/for outreach.
Done when
Each entry page has a unique OG image and a copyable badge snippet, and a few publishers display it.
- 主要語言
- JavaScript
- 星號
- 58
- 分支
- 15
- 平均合併
- 18 小時 42 分鐘
- 30 天內合併 PR
- 11
環境準備
- 沒有 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 天內回覆
-
correction
難度 2/5 1-3 小時 新手友好度 57/100
TMHSDigital/Free-Game-Dev-Assets#162 ·
維護者通常 1 天內回覆
-
marketing priority: low
難度 2/5 1-3 小時 新手友好度 55/100
TMHSDigital/Free-Game-Dev-Assets#152 ·
維護者通常 1 天內回覆
查看 TMHSDigital/Free-Game-Dev-Assets 的全部 Issue
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 92/100
danilogiles/enki-browser#113 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 85/100
維護者通常 1 天內回覆
-
ux
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆
-
bug triage
難度 2/5 1-3 小時 新手友好度 74/100
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 95/100
weavefox/awesome-opc#29 ·
維護者通常 1 天內回覆