Skip to content

[FEATURE] Add community project submission template and README CTA - #485

Open
John McCall (lowlydba) wants to merge 4 commits into
mainfrom
lowlydba-community-submission-issue-form
Open

[FEATURE] Add community project submission template and README CTA#485
John McCall (lowlydba) wants to merge 4 commits into
mainfrom
lowlydba-community-submission-issue-form

Conversation

@lowlydba

Copy link
Copy Markdown
Contributor

Submitting a community project meant opening a blank issue or PR and hand-editing community/community-projects.json. There was no guided path.

Adds .github/ISSUE_TEMPLATE/community-project.yaml, an issue form with fields matching the community-projects.json entry schema: title, url, creator, creatorUrl (optional), release, and tags.

Adds a centered call-to-action button above the fold in the README linking to the new template, styled with the OMF brand blue (#4051CC).

Fixes #484

Link a new issue form (community-project.yaml) collecting the fields
community-projects.json needs, and add a centered call-to-action
button above the fold in the README so it's the first thing a visitor
sees.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Signed-off-by: John McCall <john@overturemaps.org>
Signed-off-by: John McCall <john@overturemaps.org>
Signed-off-by: John McCall <john@overturemaps.org>
@lowlydba
John McCall (lowlydba) marked this pull request as ready for review August 14, 2026 17:05
@lowlydba
John McCall (lowlydba) requested a review from a team as a code owner August 14, 2026 17:05
Copilot AI lite review requested due to automatic review settings August 14, 2026 17:05
@github-actions

github-actions Bot commented Aug 14, 2026

Copy link
Copy Markdown

Super-linter summary

Language Validation result
JAVASCRIPT_ES Pass ✅
MARKDOWN Pass ✅
NATURAL_LANGUAGE Pass ✅
SQLFLUFF Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter

@github-actions

github-actions Bot commented Aug 14, 2026

Copy link
Copy Markdown

🗺️ OMF Docs previews are live!

🆕 Auto-gen schema site (beta) https://staging.overturemaps.org/docs/pr/485/index.html
🗂️ Auto-gen schema ref main@2a6170c
🌍 Repo schema site https://staging.overturemaps.org/docs/pr/485-no-autogen/index.html
🕐 Updated Aug 14, 2026 17:20 UTC
📝 Commit 72cdcc7

Auto-gen schema site is now available. This is an early preview of a future workflow where we will automatically generate and publish reference docs for the Overture Maps Format schema.

The auto-gen schema site may contain incomplete or inaccurate information as we are still refining the generation process, so please compare against the repo schema site and refer to the official Overture documentation for authoritative information.

Note

♻️ This preview updates automatically with each push to this PR.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR introduces a guided submission path for adding community projects by adding a dedicated GitHub issue form and surfacing a prominent README call-to-action that links to it, aligning with Issue #484’s request to reduce friction for submissions.

Changes:

  • Added a new GitHub issue form template for community project submissions with fields corresponding to community/community-projects.json.
  • Added a centered “Submit a community project” CTA button near the top of README.md linking to the new template.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
README.md Adds a centered CTA button linking to the community project submission issue form.
.github/ISSUE_TEMPLATE/community-project.yaml Adds a new issue form to collect community project details for later entry into community-projects.json.
Suppressed comments (1)

.github/ISSUE_TEMPLATE/community-project.yaml:50

  • community/community-projects.json stores tags as a JSON array of strings, but the form currently asks for a comma-separated string. This increases the chance of inconsistent formatting (spaces, casing) and requires extra conversion when copying into the JSON file.
  - type: input
    id: tags
    attributes:
      label: Tags
      description: Comma-separated tags describing the project (e.g. theme, language, or format).
      placeholder: "python, buildings, tutorial"

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread README.md Outdated
Comment thread README.md Outdated
Comment thread .github/ISSUE_TEMPLATE/community-project.yaml
…rl id

Signed-off-by: John McCall <john@overturemaps.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEATURE] Add community project submission template and README call-to-action

2 participants