Skip to content

CONTRIBUTING.md

Latest commit

 

History

History
25 lines (16 loc) · 1.23 KB

CONTRIBUTING.md

File metadata and controls

25 lines (16 loc) · 1.23 KB
Raw

Contributing

This atlas grows best when feedback stays reviewable, discussable, and traceable.

Feedback flow

  1. Open an issue with the Atlas feedback template for ideas, corrections, missing resources, graph-edge suggestions, or UX problems.
  2. The maintainer triages the issue: accept, ask for evidence, merge into an existing thread, or close as out of scope.
  3. Accepted ideas become a short-lived branch and pull request.
  4. The PR updates the relevant card, docs/data/graph.json, playbook, lab, or site code.
  5. If the contributor wants attribution, add them to the card front matter with contributors: [@github-handle].

Contributor attribution

Use contributors for people whose suggestion or review materially shaped a card or expansion:

contributors: ["@alice", "@bob"]

The live site renders this field on the card. GitHub PR authorship remains the source of truth for code changes.

Why issues, not a raw suggestions folder?

Issues are better for intake because visitors do not need write access, discussion is threaded, labels make triage visible, and accepted work can close the issue from a PR. The repo still keeps the durable result: updated cards, graph edges, playbooks, labs, and contributor metadata.