How to use and contribute to kola-language-packs
Install the packs, map them into your editor or lessons, and contribute translations without treating packs as a runtime.
Edition 2Revised Why editions?
kola-language-packs is shared vocabulary for African-language programming tools. The packs hold keyword maps and IDE gloss. Editors, transpilers, and learning apps can consume them. The packs are not a programming language runtime.
Today the registry covers 29 language packs, 370 logical tokens, and 15 programming targets. We publish when packs are ready to maintain in the open. Project landing: open source.
What you get
- Keyword maps across many language packs
- Gloss aimed at IDE and learning surfaces
- An npm package when you want a registry instead of a one-off ZIP
Links that stay current:
- GitHub: KolanutTechnologies/kola-language-packs
- npm: @kolanut/language-packs
- Simple contribute path: CONTRIBUTING-SIMPLE.md
How a team uses the packs
- Read the pack format in the repo README so "token" and "target" mean the same thing on your team.
- Install or vendor the published package if you need a stable registry.
- Map packs into your surface: editor gloss, lesson copy, or transpile tables. Your product owns the UX. The packs own the shared words.
- File Issues early when phrasing feels unnatural. Native-speaker correction is the quality bar.
If you are building classroom units in Yoruba, read more: teaching coding in Yoruba.
How to contribute
- Native speakers and educators can suggest translations or flag awkward phrasing via GitHub Issues. No git required.
- Developers can star the repo, watch releases, or open PRs when ready to edit packs.
- Partnerships and press can reach opensource@kolatech.africa.
Templates live on GitHub so this page does not go stale when forms change.
Schools and other tools can use the packs on their own. If you want them inside a phone-first IDE, that product is Kola Code.