Skip to content

Commit c71b64d

Browse files
Fix Pages CI and add public-facing repo chrome.
Drop duplicate Quaternius kit ids, bump EXPECTED_COUNT, ship the official CC0-1.0 legalcode, and add README badges plus issue/PR/CoC/security files so the repo looks trustworthy at 16 stars. Co-authored-by: Cursor <cursoragent@cursor.com>
1 parent 87eae38 commit c71b64d

17 files changed

Lines changed: 463 additions & 124 deletions

‎.github/ISSUE_TEMPLATE/config.yml‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
blank_issues_enabled: true
2+
contact_links:
3+
- name: Browse the catalog
4+
url: https://tmhsdigital.github.io/Free-Game-Dev-Assets/
5+
about: Search and filter sources on the website
6+
- name: Contributing guide
7+
url: https://github.com/TMHSDigital/Free-Game-Dev-Assets/blob/main/CONTRIBUTING.md
8+
about: How to add or correct a catalog entry
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
name: Correction
2+
description: Broken link, stale license, or wrong commercial/attribution flag
3+
title: "[correction] "
4+
labels: ["correction"]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: A wrong license claim is worse than a missing entry. Quote the live page.
9+
- type: input
10+
id: entry
11+
attributes:
12+
label: Catalog entry
13+
description: Filename or URL, e.g. `catalog/3d/kenney.md`
14+
placeholder: catalog/category/id.md
15+
validations:
16+
required: true
17+
- type: dropdown
18+
id: kind
19+
attributes:
20+
label: What's wrong
21+
options:
22+
- Dead / redirected URL
23+
- License text changed
24+
- Commercial or attribution flag is wrong
25+
- Should be deprecated
26+
- Other metadata
27+
validations:
28+
required: true
29+
- type: input
30+
id: source
31+
attributes:
32+
label: Live source URL
33+
validations:
34+
required: true
35+
- type: textarea
36+
id: evidence
37+
attributes:
38+
label: Evidence
39+
description: Short quote from the live page (under 15 words is enough) plus the date you checked.
40+
validations:
41+
required: true
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
name: New source
2+
description: Suggest a free, commercially usable asset library, pack, or tool
3+
title: "[source] "
4+
labels: ["new-source"]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
Check [CONTRIBUTING.md](https://github.com/TMHSDigital/Free-Game-Dev-Assets/blob/main/CONTRIBUTING.md) and search the [catalog](https://tmhsdigital.github.io/Free-Game-Dev-Assets/) first. Duplicates and paid-only marketplaces will be closed.
10+
- type: input
11+
id: name
12+
attributes:
13+
label: Name
14+
placeholder: Kenney, Poly Haven, Lucide, …
15+
validations:
16+
required: true
17+
- type: input
18+
id: url
19+
attributes:
20+
label: Publisher URL
21+
description: Primary source page, not a mirror or aggregator listing.
22+
validations:
23+
required: true
24+
- type: dropdown
25+
id: category
26+
attributes:
27+
label: Category
28+
options:
29+
- 3d
30+
- 2d
31+
- characters
32+
- audio
33+
- animation
34+
- environment
35+
- shaders-vfx
36+
- fonts
37+
- tools
38+
validations:
39+
required: true
40+
- type: input
41+
id: license
42+
attributes:
43+
label: License as stated on the live page
44+
description: Quote the short name (CC0, CC-BY-4.0, SIL OFL, custom, …). Do not guess.
45+
validations:
46+
required: true
47+
- type: dropdown
48+
id: commercial
49+
attributes:
50+
label: Commercial / game use
51+
options:
52+
- Explicitly allowed
53+
- Explicitly forbidden
54+
- Unclear / per-file
55+
- Video/YouTube only (not games)
56+
validations:
57+
required: true
58+
- type: textarea
59+
id: notes
60+
attributes:
61+
label: Why it belongs
62+
description: What production need it closes, and any license traps you already spotted.

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
## Type
2+
3+
- [ ] New catalog entry
4+
- [ ] License / metadata correction
5+
- [ ] Docs or site
6+
7+
## Checklist
8+
9+
- [ ] Copied `catalog/TEMPLATE.md` (new entries)
10+
- [ ] `id` is unique across the whole catalog
11+
- [ ] Live license checked today; `active` entries have dated `## Evidence`
12+
- [ ] Bumped `EXPECTED_COUNT` in `site/validate.mjs`
13+
- [ ] `node site/validate.mjs` passes

‎.github/workflows/ci.yml‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
name: Validate catalog
2+
3+
on:
4+
pull_request:
5+
push:
6+
branches: [main]
7+
paths:
8+
- "catalog/**"
9+
- "docs/**"
10+
- "site/**"
11+
- "README.md"
12+
- ".github/workflows/ci.yml"
13+
14+
jobs:
15+
validate:
16+
runs-on: ubuntu-latest
17+
steps:
18+
- name: Checkout
19+
uses: actions/checkout@v4
20+
21+
- name: Setup Node
22+
uses: actions/setup-node@v4
23+
with:
24+
node-version: "20"
25+
26+
- name: Validate catalog
27+
run: node site/validate.mjs

‎CODE_OF_CONDUCT.md‎

Lines changed: 128 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,128 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, caste, color, religion, or sexual
10+
identity and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment:
18+
19+
- Demonstrating empathy and kindness toward other people
20+
- Being respectful of differing opinions, viewpoints, and experiences
21+
- Giving and gracefully accepting constructive feedback
22+
- Accepting responsibility and apologizing to those affected by our mistakes,
23+
and learning from the experience
24+
- Focusing on what is best not just for us as individuals, but for the overall
25+
community
26+
27+
Examples of unacceptable behavior:
28+
29+
- The use of sexualized language or imagery, and sexual attention or advances of
30+
any kind
31+
- Trolling, insulting or derogatory comments, and personal or political attacks
32+
- Public or private harassment
33+
- Publishing others' private information, such as a physical or email address,
34+
without their explicit permission
35+
- Other conduct which could reasonably be considered inappropriate in a
36+
professional setting
37+
38+
License arguments belong in issues with quotes from the live source page.
39+
Personal attacks over a license reading do not.
40+
41+
## Enforcement Responsibilities
42+
43+
Community leaders are responsible for clarifying and enforcing our standards of
44+
acceptable behavior and will take appropriate and fair corrective action in
45+
response to any behavior that they deem inappropriate, threatening, offensive,
46+
or harmful.
47+
48+
Community leaders have the right and responsibility to remove, edit, or reject
49+
comments, commits, code, wiki edits, issues, and other contributions that are
50+
not aligned to this Code of Conduct, and will communicate reasons for moderation
51+
decisions when appropriate.
52+
53+
## Scope
54+
55+
This Code of Conduct applies within all community spaces, and also applies when
56+
an individual is officially representing the community in public spaces.
57+
58+
## Enforcement
59+
60+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
61+
reported by opening a GitHub issue on this repository or by contacting the
62+
maintainer via GitHub ([@TMHSDigital](https://github.com/TMHSDigital)).
63+
64+
All complaints will be reviewed and investigated promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning, providing clarity around the
80+
nature of the violation and an explanation of why the behavior was
81+
inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
84+
85+
**Community Impact**: A violation through a single incident or series of
86+
actions.
87+
88+
**Consequence**: A warning with consequences for continued behavior. No
89+
interaction with the people involved, including unsolicited interaction with
90+
those enforcing the Code of Conduct, for a specified period of time. This
91+
includes avoiding interactions in community spaces as well as external channels
92+
like social media. Violating these terms may lead to a temporary or permanent
93+
ban.
94+
95+
### 3. Temporary Ban
96+
97+
**Community Impact**: A serious violation of community standards, including
98+
sustained inappropriate behavior.
99+
100+
**Consequence**: A temporary ban from any sort of interaction or public
101+
communication with the community for a specified period of time. No public or
102+
private interaction with the people involved, including unsolicited interaction
103+
with those enforcing the Code of Conduct, is allowed during this period.
104+
Violating these terms may lead to a permanent ban.
105+
106+
### 4. Permanent Ban
107+
108+
**Community Impact**: Demonstrating a pattern of violation of community
109+
standards, including sustained inappropriate behavior, harassment of an
110+
individual, or aggression toward or disparagement of classes of individuals.
111+
112+
**Consequence**: A permanent ban from any sort of public interaction within the
113+
community.
114+
115+
## Attribution
116+
117+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+
version 2.1, available at
119+
https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
120+
121+
Community Impact Guidelines were inspired by
122+
[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
123+
124+
[homepage]: https://www.contributor-covenant.org
125+
126+
For answers to common questions about this code of conduct, see the FAQ at
127+
https://www.contributor-covenant.org/faq. Translations are available at
128+
https://www.contributor-covenant.org/translations.

‎CONTRIBUTING.md‎

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,8 @@
22

33
This repo catalogs **links and metadata** for free (preferably commercially usable) game assets and related tools. It does not host binary asset dumps.
44

5+
Please follow the [Code of Conduct](CODE_OF_CONDUCT.md).
6+
57
## What belongs here
68

79
- Asset libraries, packs, and aggregators with a clear free tier
@@ -24,11 +26,14 @@ One new markdown file is enough — the website rebuilds from frontmatter on dep
2426
1. Copy [`catalog/TEMPLATE.md`](catalog/TEMPLATE.md).
2527
2. Save it as `catalog/<category>/<id>.md` using a short kebab-case `id`.
2628
3. Fill every frontmatter field. Prefer primary URLs over mirror/aggregator pages.
27-
4. Verify the license on the live source page the day you submit.
28-
5. For `status: active`, include an `## Evidence` line with a short quote from that page.
29-
6. Optional 2D/UI fields: `grid_dimensions`, `camera_perspective`, `hardware_tags`, `attribution_string` (see [`TEMPLATE.md`](catalog/TEMPLATE.md)).
30-
7. Optional: add a line to the matching category `README.md` for GitHub browsing (the site does not require this).
31-
8. Optional: add the `id` to `site/config.json` → `featured` to pin it under Safe starting points.
29+
4. `id` must be unique across the **whole** catalog. A mixed kit already listed in another category is a duplicate, not a second entry.
30+
5. Verify the license on the live source page the day you submit.
31+
6. For `status: active`, include an `## Evidence` line with a short quote from that page.
32+
7. Bump `EXPECTED_COUNT` in [`site/validate.mjs`](site/validate.mjs) by the number of files you added (or lowered if you removed some).
33+
8. Run `node site/validate.mjs` — it must exit 0.
34+
9. Optional 2D/UI fields: `grid_dimensions`, `camera_perspective`, `hardware_tags`, `attribution_string` (see [`TEMPLATE.md`](catalog/TEMPLATE.md)).
35+
10. Optional: add a line to the matching category `README.md` for GitHub browsing (the site does not require this).
36+
11. Optional: add the `id` to `site/config.json` → `featured` to pin it under Safe starting points.
3237

3338
### Frontmatter rules
3439

0 commit comments

Comments
 (0)