Good First Issues
The best ways to make your first contribution to TLD.
Types of contributions
| Type | Examples | Difficulty |
|---|---|---|
| Fix a typo | README, lab content.md, doc pages | Very easy |
| Improve a lab README | Add more context, clearer hints | Easy |
| Fix a validator bug | Edge case in validator.sh | Easy–Medium |
| Write a new beginner lab | New track concept, guided hints | Medium |
| Improve error messages | CLI error output clarity | Medium |
| Add a new CLI command | New flag, new subcommand | Hard |
GitHub labels
good first issue — safe for first contributorsStart Here
help wanted — maintainers need assistanceHelp Wanted
lab-request — community lab ideasLabs
bug — something is brokenBug
Ask before you build
For anything bigger than a typo fix, open a GitHub issue first and describe what you plan to do. This prevents duplicate work and ensures your contribution fits the project direction.