Practice open source content vocabulary: README-driven development, docs as code, contribution guides, hackathon vocabulary, seeking maintainers, and good first issues.
0 / 10 completed
1 / 10
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 / 10
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 / 10
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 / 10
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 / 10
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.
6 / 10
Sarah from the frontend team is reviewing your pull request. She comments: 'This change introduces a new dependency on lodash. Can you provide some context around why this was chosen and how it integrates with our existing architecture?' What does Sarah likely mean when asking for this information?
Sarah is asking for justification beyond just syntax. She's assessing the *reasoning* behind using lodash – whether it's truly needed and how it aligns with the project's goals. The incorrect options focus on technical details (syntax) or tasks (bug fixes) that aren't directly relevant to her request for context.
7 / 10
Mark sends a Slack message: 'Hey team, just bumping this PR. The build is failing with a cryptic error related to the graphql-js package. Anyone see anything?' What does Mark's message indicate about the state of his pull request?
Mark's phrasing – 'bumping,' 'failing with a cryptic error' – strongly suggests a problem. He's signaling that the PR isn't yet ready and requires investigation. The other options misinterpret common Slack communication related to code reviews; 'bumping' implies an issue has arisen.
8 / 10
You are examining the API response from a documentation service when researching how to use a particular library. The response includes the following JSON snippet:
{
"version": "1.2.3",
"description": "Provides functions for interacting with the Redis server.",
"usage_examples": [
"client = RedisClient();",
"data = client.get('key')"
]
}
What does 'usage_examples' in this response likely represent?
'Usage examples' provides concrete demonstrations, often in code form. This is a common practice for API documentation to show developers *how* to apply the library's functionality quickly. While it contains snippets (option 3), its primary purpose is illustrative, not just providing isolated code fragments.
9 / 10
David is contributing to an open source project and includes the following in his pull request description:
'Fixed a typo in the documentation. This PR also includes updated tests for this functionality.' What does David's statement primarily highlight about his contribution?
David's description emphasizes that his contribution was about correcting a defect and confirming it with tests. This aligns with the importance of fixing issues and verifying changes in open source projects – ensuring stability and quality. The other options describe more substantial development tasks.
10 / 10
During a standup meeting, Emily says: 'I'm working on adding support for GraphQL to the API. I've created a draft contribution guide and am looking for feedback on the proposed schema.' What does Emily mean by creating a 'contribution guide'?
A 'contribution guide' (like `CONTRIBUTING.md`) is a document that outlines *how* others can contribute to a project – typically covering coding standards, testing procedures, and workflow expectations. Emily's statement indicates she wants feedback on the process of contributing to her work, not just the technical details themselves.
What does this Technical Content Creation Language exercise cover?
This exercise, "Open Source Content Vocabulary Quiz", tests your understanding of technical content creation language vocabulary and phrasing through 10 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this Technical Content Creation Language exercise for?
It's designed for IT professionals and learners who want to sound natural discussing technical content creation language topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more Technical Content Creation Language exercises?
Browse the full Technical Content Creation Language exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.