Practice open source content vocabulary: README-driven development, docs as code, contribution guides, hackathon vocabulary, seeking maintainers, and good first issues.
0 / 5 completed
1 / 5
What is 'README-driven development'?
README-driven development (popularized by Tom Preston-Werner) treats the README as a specification: write how you want the project to look from the outside before implementing it. This forces clarity about purpose and interface before getting lost in implementation details.
2 / 5
What does 'docs as code' mean in open source practice?
'Docs as code' applies software engineering practices to documentation: docs live in the same Git repository as the code, changes are reviewed in PRs, automated tests check for broken links and outdated code examples, and docs deploy alongside releases. This keeps docs current and collaborative.
3 / 5
What is a 'good first issue' label on GitHub and what purpose does it serve?
'Good first issue' labels are a deliberate contributor onboarding tool. Maintainers select issues with limited scope, clear requirements, and available guidance so new contributors can make a meaningful contribution without needing deep codebase knowledge. It is a standard open source contribution funnel entry point.
4 / 5
What is a 'contribution guide' (CONTRIBUTING.md) in an open source project?
CONTRIBUTING.md is the contributor onboarding document. It covers: how to set up the development environment, coding style expectations, how to run tests, commit message format, PR submission process, and what happens during review. Projects without a clear CONTRIBUTING.md have higher contributor abandonment.
5 / 5
In open source vocabulary, what does a project mean by 'looking for good first issues'?
When a project actively curates 'good first issues', it is intentionally investing in contributor pipeline health. Maintainers scope and document issues specifically to be approachable — making this label both a recruiting tool and a signal that the project is actively welcoming new contributors.