# Community submission process

1. A contributor creates a repository from the official template and builds a
   public project that uses NamoID Hosted Auth as its application sign-in system.
2. They open the **Submit a community build** issue with repository, pinned SHA,
   demo, summary, technologies, NamoID features, and license.
3. Automation verifies the public repository and commit.
4. A maintainer applies the checklist in `RUBRIC.md`.
5. For an approved project, the maintainer adds one record to
   `data/submissions.json` in a pull request.
6. Validation confirms that the record is complete and not duplicated.
7. Merge regenerates the gallery and every challenge page.

Multiple builds for one challenge are expected. Each build is a separate record
with the same `challengeId` and its own unique repository URL, slug, and pinned
commit.

Repository owners may request a correction, new pinned commit, or removal.