Make this better for the next learner
Nyxora Sync is free and open source. Every fix, explanation, resource, and shared project compounds — someone you will never meet gets unstuck because of it.
Ways to help
No contribution is too small. Pick what fits your time.
Improve a lesson
Fix an error, sharpen an explanation, add a worked example, or write a missing lesson. The authoring guide covers the format.
Get startedAdd a free resource
A tutorial, video, or reference that earned its place. Include why it helps and what it assumes.
Get startedShare a project
The showcase is community content too. Post what you built and explain the part that took the longest.
Get startedReport a bug
Broken code sample, incorrect claim, inaccessible control, or a 404. Include the page and what you expected.
Get startedTranslate
Lessons are plain MDX. Translate one lesson at a time and keep code samples untouched.
Get startedHelp in discussions
Answer a question under a lesson. Explaining a concept is the best test of whether you know it.
Get startedHow a lesson contribution works
- 1
Pick one small thing
A typo, a confusing paragraph, one resource. Small pull requests get reviewed fastest.
- 2
Fork and branch
Create a branch named after the change, for example docs/fix-jwt-typo. Keep the diff focused.
- 3
Follow the lesson format
Lessons use MDX components and a fixed structure: hook, sections, examples, callouts, quiz, exercise, summary.
- 4
Open a pull request
Explain what changed and why. Link the lesson or issue. A maintainer reviews and merges.
Resource standards
- Every code sample must run with the versions stated in the lesson.
- Prefer official documentation and free resources; no paywalled links.
- Teach one idea at a time, with a concrete example before theory.
- Accessibility is not optional: labels, focus states, and readable contrast.
- Credit sources and respect their licenses.
Translating lessons
Open an issue naming the lesson and language first, so two people do not translate the same file. Keep code blocks, component names, and technical terms in English unless the term is commonly translated.
Translations live beside the English lesson and are linked from the lesson page once reviewed.
Reviewing pull requests
Running the code, checking claims against current docs, and flagging unclear explanations is as valuable as writing. Comment with the specific sentence and a suggested fix.
Open pull requestsNot sure where to start?
Open an issue describing what confused you. Confusion is a bug report — it usually points at the exact paragraph that needs work.