Skip to content
Specimen Atlas of Research Peptides81 plates · MIT
PeptidesDBan atlas

A community manuscript

Contribute

Every plate has a maintainer of one and contributors of many.

§ 01 · The thesisA peer-reviewed reference, written in public.

PeptidesDB is not a peptide store, a forum, or a SaaS app. It is a community-edited atlas. Every claim points to a paper. Every paper points to its DOI or PubMed entry. Every plate cites its sources. When a claim cannot be cited yet, it is marked uncited so a future contributor can close the gap.

The five guarantees the atlas makes to its readers are documented in DESIGN.md § 1. The mechanical rules contributors follow to keep those guarantees true are documented below.

§ 02 · What a contribution looks likeSmall, well-cited, reversible.

  1. Add a citation. A claim on a plate is unsourced or weakly sourced and you have a paper that supports it. PubMed ID or DOI is the unit of currency. Vendor pages are not citations.
  2. Correct a claim. A figure is wrong. A mechanism description is outdated. An evidence level overstates what the literature supports. Bring a citation if you have one — if not, the maintainer will help find one.
  3. Add a peptide plate. A peptide with a published clinical or preclinical evidence base is missing. Open a plate proposal with two to five starter citations.
  4. Fix a typo or formatting issue. Spelling, grammar, broken link, layout glitch. One-line edits welcome.

§ 03 · The flowFrom a paper you read to a plate that cites it.

  1. Find the plate. Each plate page (e.g. /p/tesamorelin) has a colophon at the bottom with Edit on GitHub →. That link opens the plate’s YAML in GitHub’s editor.
  2. Make the change. Each plate is a single YAML file in content/peptides/<slug>.yaml. Citations are referenced by ID; the registry lives in content/refs.yaml.
  3. Open a pull request. GitHub provides a one-click flow: edit, add a commit message, propose a change. The audit workflow runs the schema gate automatically (bun run audit:trust). A maintainer reviews and merges, or asks a question.
  4. See it live. Once merged to main, Vercel rebuilds the affected plate within a minute. Your @handle joins the colophon.

A short screencast walking through this flow is planned for a future release.

§ 04 · The schemaOne YAML, one peptide, one source of truth.

The full plate YAML schema is defined as a Zod schema in src/lib/schemas/peptide.ts. The audit script enforces it at build time and on every PR.

New plates start from content/peptides/_template.yaml. Read CONTRIBUTING.md for the field-by-field walkthrough and DESIGN.md for the editorial conventions.

§ 05 · RecognitionNamed in the colophon. Linked to your work.

Each contributor is listed in the colophon of every plate they have touched, by GitHub handle, linked to their profile. The atlas does not paywall, gate, or rebrand contributor work. What you write here stays here, under the project’s MIT license, with your name beside it.

Maintainers operate under the Contributor Covenant 2.1.