We label every beginner-friendly task and promise a first review within three days. You do not need to know the whole codebase: a documentation fix or an extra test is a real contribution, and your name goes in the release notes.

Choose an issue labelled good first issue, or open one describing what you would like to change. Comment that you are taking it so nobody duplicates the work.
Fork the repository, run npm install and npm test to check your setup, and make the change. Add a test, or a docs example, that shows it working.
Describe what changed and why. Automated checks run the tests, the linter and a build of the documentation site, and the results appear in a minute.
A maintainer replies within three days. Reviews are about the change, never the person, and most pull requests are merged after one round of edits.
A small selection of open tasks. Each one links to a thread with hints from the maintainer who knows the area.
5 open tasks
The lists page shows one level only. Add a three-level example, check it renders correctly in HTML and PDF, and link it from the tutorial.
The English page is stable. Copy it into the pt folder, translate it and run the spell check. Native reviewers from São Paulo will read it.
A long footnote that crosses a page resets the counter. A failing test is already in the repository; the fix is in the pagination step.
The error says only that the theme was not found. It should list the installed themes and suggest the closest name.
The proposal is accepted. Implement the parser rule, the HTML output and the PDF styling, and add tests for the edge cases listed in the thread.
No contributor agreement is required. You certify with a sign-off line that you wrote the change or have the right to submit it.
Be kind, assume good faith and keep discussions about the work. Reports go to two maintainers who are not involved in the thread.
The project fund pays small bounties for security reports and larger features agreed in advance. Ask in the issue before you start.