Submitting a community project today means opening a blank issue or PR and hand-editing community/community-projects.json. There's no guided path, so it doesn't happen often.
Add a dedicated issue form template (.github/ISSUE_TEMPLATE/community-project.yaml) with fields matching the entry schema in community-projects.json: title, url, creator, creatorUrl, release, and tags. Link to it from a button above the fold in the README so it's the first thing a visitor sees.
Acceptance criteria:
- New issue template collects all fields required to add an entry to
community-projects.json without extra back-and-forth.
- README has a graphical call-to-action button, visible without scrolling, linking to the new template.
Submitting a community project today means opening a blank issue or PR and hand-editing
community/community-projects.json. There's no guided path, so it doesn't happen often.Add a dedicated issue form template (
.github/ISSUE_TEMPLATE/community-project.yaml) with fields matching the entry schema incommunity-projects.json:title,url,creator,creatorUrl,release, andtags. Link to it from a button above the fold in the README so it's the first thing a visitor sees.Acceptance criteria:
community-projects.jsonwithout extra back-and-forth.