Add a CC0 model pack (Quaternius or KayKit) to the pack library — no app code required, great first contribution if you like curating assets.
How packs work: the Explorer loads packs from the separate theprototype-app/packs repo via CDN — a pack is a folder with a manifest (name, items, attribution/license) + thumbnails + model files. PACKS.md in that repo documents the exact format; the existing packs are the reference.
Task (the PR goes to the packs repo; this issue tracks it here for visibility)
- Pick a coherent CC0 set: Quaternius (Ultimate packs) or KayKit — verify the specific set is CC0.
- Create the pack folder: curated selection (a coherent 15–40 items beats a 300-file dump), manifest with attribution + license rows filled in, thumbnails.
- Mind file sizes: small metadata/thumbs go via jsDelivr; large
.glb files are served via raw.githubusercontent (see how the Khronos pack handles it).
Acceptance
- Pack browses in the Explorer with thumbnails, items drag into the scene.
- Attribution shows on the pack (source/author/license).
- License verified CC0 in the PR description with a link to the source page.
Pointers: PACKS.md · CONTRIBUTING.md. Questions → Discussions.
Add a CC0 model pack (Quaternius or KayKit) to the pack library — no app code required, great first contribution if you like curating assets.
How packs work: the Explorer loads packs from the separate
theprototype-app/packsrepo via CDN — a pack is a folder with a manifest (name, items, attribution/license) + thumbnails + model files.PACKS.mdin that repo documents the exact format; the existing packs are the reference.Task (the PR goes to the packs repo; this issue tracks it here for visibility)
.glbfiles are served via raw.githubusercontent (see how the Khronos pack handles it).Acceptance
Pointers: PACKS.md · CONTRIBUTING.md. Questions → Discussions.