Choose a first contribution
Start with a change whose behavior you can explain and check locally. Useful contributions include docs, synthetic fixtures, small parser tests, examples, and reproducible bug reports. Search current issues and pull requests before choosing a task: the briefs below are candidate starting points, not open issues or promises that work remains available.
Read CONTRIBUTING.md and the triage guide first. Avoid starting with payment, access-control, webhook-signature, migration-schema, or release-publication work. Those areas need maintainer review and broader qualification.
Candidate task briefs
Section titled “Candidate task briefs”The maintainer should check for duplicates, current ownership, and scope before turning a brief into a labeled issue.
Add a duplicate-header import regression
Section titled “Add a duplicate-header import regression”The normalized import guide documents that the first instance of a recognized
CSV header wins. Add a focused regression to
packages/create-stratolms/tests/unit/import.test.ts for a file with duplicate
email or course headers. Reproduce with a synthetic .test address and
assert the current documented behavior. Keep the implementation and fixtures
free of real learner data.
Acceptance: the regression proves which column is selected and fails if that contract changes without an intentional docs update. Run:
pnpm exec vitest run --config vitest.unit.config.ts packages/create-stratolms/tests/unit/import.test.tsAdd a public-doc anchor regression
Section titled “Add a public-doc anchor regression”The docs renderer has compatibility routes for older public URLs. Review
scripts/verify-doc-links.mjs and the public docs route tests, then add a
focused case for an encoded path or a heading anchor with punctuation. Do not
add research, course lesson, or maintainer-only files to the public document
manifest.
Acceptance: the local docs check catches the broken mapping or fragment,
and the existing public route still renders. Run pnpm verify:docs and the
narrow docs route test named in the current test file. Confirm first that this
work is not already owned by an open pull request.
Clarify one safe Astro integration recipe
Section titled “Clarify one safe Astro integration recipe”Pick one integration already present in the compatibility fixture or starter
and add a small user-facing example in
docs/integrations/writing-safe-integrations.md. Keep it outside /learn,
declare any external hosts in stratolms.config.mjs, and preserve the build
guard as the final integration. Do not make a package or runtime feature change.
Acceptance: the example uses current Astro APIs, the integration fixture
continues to build, and it does not loosen CSP or make a protected route static.
Run pnpm test:integrations and pnpm test:integration-guard after coordinating
the shared build slot with the maintainer.
Before opening a pull request
Section titled “Before opening a pull request”Keep the patch narrow, run its listed check, and include the exact command and result in the pull request. The full repository gate and release qualification are maintainer-coordinated; see the release procedure and the owner qualification runbook. Do not claim a live provider, registry, or deployment result based on a local test.