This repo has no root README.md and no CONTRIBUTING.md — the only root-level docs are ASSUMPTIONS.md, TODO.md, and PR_DESCRIPTION.md. There is a genuinely thorough docs/ folder (docs/DOCUMENTATION_INDEX.md, docs/DEPLOYMENT.md, etc.), but nothing at the entry point tells a new contributor it exists, or walks them through local setup.
Given the repo actively recruits outside contributors (existing good first issue / bounty-program labels), the lack of an onboarding doc is a real gap.
Task
- Add a root
README.md: what the project is, link to docs/DOCUMENTATION_INDEX.md, quickstart (env vars from .env.example, docker-compose.yml, npm run dev).
- Add
CONTRIBUTING.md: local setup, npm test / npm run lint / npm run typecheck, PR conventions (see docs/PR_GIT_HOOKS.md and .husky/), how issues map to PRs.
Good first issue.
This repo has no root
README.mdand noCONTRIBUTING.md— the only root-level docs areASSUMPTIONS.md,TODO.md, andPR_DESCRIPTION.md. There is a genuinely thoroughdocs/folder (docs/DOCUMENTATION_INDEX.md,docs/DEPLOYMENT.md, etc.), but nothing at the entry point tells a new contributor it exists, or walks them through local setup.Given the repo actively recruits outside contributors (existing
good first issue/ bounty-program labels), the lack of an onboarding doc is a real gap.Task
README.md: what the project is, link todocs/DOCUMENTATION_INDEX.md, quickstart (env vars from.env.example,docker-compose.yml,npm run dev).CONTRIBUTING.md: local setup,npm test/npm run lint/npm run typecheck, PR conventions (seedocs/PR_GIT_HOOKS.mdand.husky/), how issues map to PRs.Good first issue.