Start with a clear contributor profile
A contributor record connects a display name and GitHub profile to the work in the collection. Use an identity you can substantiate and explain your role in creating the template. Preserve the attribution and licenses of other people’s work where they apply.
The original collection is published under build.host’s publisher profile. That does not turn every referenced design product, photographer, or font author into a build.host contributor or endorser.
Verification is reviewed separately
Maintainers review the GitHub identity, ownership of submitted work, and contribution quality before granting verified status. The contributor list is protected by code-owner review. A PR proposing verification does not approve itself, and template-level verification fields are rejected by the catalog checks.
A badge is not a universal guarantee of functionality, security, or suitability. Each template’s description, supplied files, stated limitations, and review evidence remain important to someone choosing it.
Contribution, review, and access are different roles
You can contribute through a fork without access to the private platform. A verified profile does not automatically grant write access to the template repository. A category reviewer is a maintainer-assigned responsibility with its own repository permissions.
This separation lets authors receive credit while keeping publication and account access deliberate. Changes to contributor verification, categories, and publishing configuration remain reviewable in source history.