marketing: a distribution checklist (awesome lists, engine communities, dataset hubs) and a launch post
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 25/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- github, javascript
- 領域
- content
研究方向
Start by reading the README positioning paragraph and the existing website, launch assets, and FUNDING.yml; the issue names no code entry point or tests. Create docs/distribution.md and track dated links for completed listings, dataset publications, and launch posts. Done means the checklist records each completed item and stars or referral traffic show a step change.
由索引模型根據 Issue 內容生成。
描述
Why it matters
57 stars and 9 forks, with a clear differentiator (dated, quoted licence readings) against the much larger lists the README names. Nothing records where the project has been announced or listed. Getting into the lists people already use, and into the places where "is this free for commercial use?" is asked weekly, is the cheapest growth available, and FUNDING.yml is in place to convert some of it.
Evidence
- README positioning paragraph names magictools and awesome-gamedev.
- Topics (12), website badge and OG card exist; the launch assets are ready.
Suggested approach
Create docs/distribution.md as a living checklist and work it:
- PRs adding the catalog to magictools, awesome-gamedev, awesome-godot, awesome-unity, awesome-unreal, awesome-cc0, and engine docs "community resources" pages.
- Publish
data.json/catalog.csvas a CC0 dataset on Hugging Face and Kaggle with the schema. - One post each: r/gamedev and r/godot, the Godot forum, itch.io community, Hacker News "Show HN", Mastodon/Bluesky gamedev.
- A short page on the site ("Why every entry quotes the licence") for the posts to land on.
- Ask listed publishers to link back (badge issue).
Done when
The checklist has dates and links for each completed item, and stars or referral traffic show a step change.
- 主要語言
- 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
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
bug good first issue query-log web
難度 2/5 1-3 小時 新手友好度 85/100
ferrous-networking/ferrous-dns#326 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 67/100
Ylianst/MeshCentral#8294 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
維護者通常 1 天內回覆
-
enhancement good first issue help wanted
難度 2/5 1-3 小時 新手友好度 76/100
yunaremaia/jsonl-cli#1 · 1 則留言 ·