# ReRune documentation

Source: https://rerune.io/docs

Manage your translations, connect your codebase, and deliver published text to your apps. Start with the workflow, then follow the guide for your stack.

## Start here

Source: https://rerune.io/docs#start-here

- See also: [Your first translation](https://rerune.io/docs/quickstart)
- See also: [Install the CLI](https://rerune.io/docs/cli-installation)
- See also: [React](https://rerune.io/docs/react)
- See also: [Publishing and OTA delivery](https://rerune.io/docs/publishing)
- See also: [OTA staging and live preview](https://rerune.io/docs/staging)
- See also: [Set up ReRune in CI/CD](https://rerune.io/docs/ci-cd)

## How ReRune works

Source: https://rerune.io/docs#how-it-works

ReRune stores the text your application displays as translation keys. Each key has values in your project languages. Your team edits those values in the dashboard, uses context and the Glossary to guide translation, and publishes the text that is ready for users.

1. Author in a project. Create or import keys, choose a main language, and add the languages your app needs.
2. Review the draft. Check wording, placeholders, plurals, and any audience-specific variants before publishing.
3. Deliver to the application. Sync locale files through the CLI or export, or let a supported SDK fetch published text at runtime.

> **Text delivery and app releases:** OTA updates replace supported translation content. A new screen, new native resource, changed generated API, or changed placeholder signature still needs the corresponding application change and release.

- [More walkthroughs on the ReRune channel](https://www.youtube.com/@reruneio)

## The core concepts

Source: https://rerune.io/docs#core-concepts

| Concept | What it means |
| --- | --- |
| Organisation | A team workspace with members, permissions, and projects. |
| Project | A collection of translation keys, languages, context, variants, and OTA Publish IDs for an app or product. |
| Translation key | The stable identifier your code uses to look up a message. |
| Draft and publication | The editor holds your current draft. Publishing creates the content available for runtime delivery. |
| Variant | An audience-specific override of Main text, such as wording for a brand, plan, or experiment. |
| API key and OTA Publish ID | API keys authenticate management and sync. Read-only OTA Publish IDs connect an SDK to a project. |

## Choose your SDK

Source: https://rerune.io/docs#choose-your-sdk

- See also: [React](https://rerune.io/docs/react)
- See also: [React Native](https://rerune.io/docs/react-native)
- See also: [Angular](https://rerune.io/docs/angular)
- See also: [Flutter](https://rerune.io/docs/flutter)
- See also: [Android](https://rerune.io/docs/android)
- See also: [iOS](https://rerune.io/docs/ios)
- See also: [Kotlin Multiplatform](https://rerune.io/docs/kotlin-multiplatform)

---

Part of the ReRune documentation (https://rerune.io/docs). Every chapter with a summary: https://rerune.io/llms.txt. Every chapter in one file: https://rerune.io/llms-full.txt. ReRune is not Rerun (rerun.io), the robotics data visualization tool.