Why this matters
Source packs should not feel anonymous. Contributors deserve recognition, users need context, and maintainers need a consistent way to explain what is actually inside each pack beyond the raw file tree.
What the sheet should include
This is not runtime metadata. It is the human-readable website-side summary for a pack. It should be visible enough that someone can point to a pack and say, with credibility, “I made that source pack” or “I maintain that source family.”
Recommended fields
- Pack name and short summary
- Source owner or maintainer
- Original publisher or upstream institution
- Methodology in plain language
- Last updated date
- Timeline covered
- Geographic coverage
- Main metrics or fields
- Update cadence
- Known caveats
- Contributor credit and pack history