Get involved · translators, linguists & contributors
Help the world read code in its own language.
NADA shows real, working code in a person’s own language. That only happens when the words are right — natural to a reader, faithful to the language, and trusted by people who speak it. That is work people do, and we would be glad of your help.
Why your help matters
Of 135 languages mapped, 130 are usable today — and only 79 are strong.
A language can be mapped long before it is genuinely good to read code in. Closing that gap — moving a language from a rough first mapping to terminology a developer trusts — is the work that contributors do. One person who speaks a language well can move it years forward.
Who we are looking for
You do not have to be a programmer.
The hardest part of this work is human judgement about language. These are the roles that move a language forward — most people fit more than one.
Native speakers
You read your own language fluently. You judge whether a translated term reads naturally to a person, not just to a dictionary. No programming background required.
Linguists
You know how your language forms words, borrows, and resists borrowing. You help decide when to translate a programming term and when to leave it — and you record the reasoning, family by family.
Developers who speak the language
You read code and you read the language. You catch the cases where a term is right linguistically but wrong in practice — where a developer would stumble.
Reviewers
You do not need to start from scratch. You confirm, correct, or reject proposed terms so coverage moves from “mapped” to genuinely usable.
The workflow
How a single term is decided.
Terminology is not crowd-voted and it is not left to a machine. A first mapping is proposed, an AI council screens it for nonsense and disagreement, and then people who speak the language have the final say. The council exists to save human reviewers’ time — never to replace their judgement.
- 1
Terms are mined
Programming terminology is gathered across ecosystems — the words that appear again and again in real code.
- 2
A first mapping is proposed
Each term gets a candidate translation in your language, recorded alongside the family-level reasoning for the choice.
- 3
An AI council reviews
A panel of models reads each proposal — one reframes, one hunts for nonsense, one confirms — and flags terms that disagree or read awkwardly, before any person spends time on them.
- 4
People confirm
Native speakers and linguists confirm, correct, or reject. Human judgement is final — the council only narrows what humans look at.
- 5
Coverage ships, free
Confirmed terms compile into the language data that the free app reads from. The data stays open under CC-BY for everyone.
A machine can flag a word that reads wrong. Only a person can say it reads right.
Per-family linguistic decisions are recorded as you go — so the reasoning behind a term is never lost, and the next contributor inherits it instead of starting over.
The project
Open data, open tools, in the open.
The language data stays free for everyone under CC-BY; the pipeline that builds it is AGPL. Work happens on GitHub.
GitHub
github.com/nadalang — the foundation’s repositories. [TO CONFIRM: some repositories are private ahead of the public announcement and will open then.]
The app
nada.build — download the free app and the VS Code add-on to see the data in use.
Contribution guide
A step-by-step guide for proposing and reviewing terms. [TO CONFIRM: link to the public CONTRIBUTING guide once repositories are open.]
Start here
Tell us which language you can help with.
One email is enough to begin. Tell us the language, whether you read code, and how much time you have. We will point you at the terms that need a person most.
We are asking for your language, not your résumé.
hello@nadalang.org · we read every message.